Example: Conversion old version of Crop to new ve
Example: Conversion from old version to the new version of Crops, Fruit&Nuts and Grapes
Because of changing protocols of data entry on modules Crops, Fruits&Nuts and Grapes, enabling of existing data from old model to the new one was necessary. The procedure of conversion will be explained in following text.
1. Step:
First step is database upgrade. After the succesful database upgrade we have to login once again. If a window shown under appears database upgrade was succesful, but for succesful conversion we have to edit certain data in database.
 |
In case you have a database on host and following window appears you should edit data which are stated in the window. After that you should ask support to upgrade the database once again.
|
2. Step:
In next step we enter all missing data.
a) Tab - Missing Crop Area:
Here we enter missing area for particular crop areas.
In old model these data are stated in Agricultural Holding - Fields, within CA tab.
In mentioned CA tab we should enter missing data for CA area.
b) Tab - Missing Areas on Crop Cycles:
In tab Missing Areas on Crop Cycles area is also missing. Fill it please.
In former model these area data are entered in Cycle menu within Crops (for Fruits&Nuts and Grapes it is within Fruits&Nuts and Grapes Cycles sub menu). Cycle area is entered within a list of CA`s in a table under a table where a list of Cycles is.
Here we enter missing data for cycle area.
c) Tab - Missing Areas on Crop Task:
In tab Missing Areas on Crop Task we enter the data of missing areas on particular task.
In old model this data was entered within menu Tasks (Crops&Vegs - Tasks). If there is somewhere this data missing, the wizard tells us and navigates us to enter this data.
In this case it is on task GNOJENJE within cycle AJDA ČEBE 2016/4, on date 25.9.2017. Area should be entered.
In old model we can easily find it using filter for cycles and dates and look for it within appropriate tab (in this case within tab Gnojenje).
In marked and field tab we enter data:
d) Tab - Non selected CA for Operation:
In this tab we get a list of cycles where we don`t have stated any crop areas on tasks:
For each cycle we have to add crop area.
This data is entered in old model within Crops&Vegs - Tasks. If data are not entered this tab opens during database upgrade.
In marked tab we have to enter CA for which we can check within Cycles menu.
In marked and field tab we enter data:
e) Tab - Missing resource types:
In this tab we need to add the correct resource Type. Because in new concept we divided self-propelled and Implements machines.
We select machines, that they have the same recourse type, and we choose the type....
After we entered all missing data we click on 
button and get the following notification:
As stated in notification, until one more upgrade we could not use new Crops module.
If after new database upgrade you don`t get this notification it means that upgrade and conversion was successful and that all data were entered properly. After the upgrade we can check it additionally in new upgraded database.
It is important to mention that the logic in new model is different then in old model. Now, for each CA we have created new Work order. Meaning that if we had cycles with many CA`s, now within conversion we`ll get many Work orders for each CA which were within the same Cycle. Meaning that for particular tasks which were created for the Cycle which had many CA`s, we shall have not one but as many Work orders as there was CA`s for this particular Task. And the data recorded within this Task will be proportionally divided within Work orders according to CA areas.
More you can find about conversion here.