This commit is contained in:
@@ -106,7 +106,9 @@ The AyaNova server only supports .json data; a .csv file is converted to json fo
|
||||
|
||||
#### Use .json if possible
|
||||
|
||||
If at all possible, we recommend using the .json format _over_ the .csv format as .json can exactly match the structure of the objects in AyaNova and imports in one step, whereas the CSV files need to be mapped on to the .json format structure before sending to the server for import / update.
|
||||
If at all possible, we recommend using the .json format _over_ the .csv format as .json can exactly match the structure of the objects in AyaNova and imports in one step and there is no possibility of mis-interpreting the type of data in each field.
|
||||
|
||||
CSV files need to be first imported and interpreted then mapped on to the .json format structure before sending to the server for import / update which is an extra step and could result in [errors](#ambiguous-csv-text-fields-should-be-quoted).
|
||||
|
||||
### Import file format
|
||||
|
||||
@@ -144,6 +146,16 @@ To ensure the integrity of the data, import will _not_ be attempted if ther are
|
||||
|
||||
CSV parsing errors come form a utility and are not translated so they will be displayed in the English language only.
|
||||
|
||||
#### Ambiguous CSV Text fields should be quoted
|
||||
|
||||
If a field should represent a text value but could contain an ambiguous value that could be interpreted as another type of data then it should be surrounded in "quotes".
|
||||
|
||||
This prevents an issue where a text field could be mis-interpreted as another type of data by the .csv import library used.
|
||||
|
||||
For example, if the text name of an object was all numbers "03456" and it wasn't quoted, the csv import would interpret it as the number 3456 (dropping the leading 0) which would then not be the same or not match to a linked object if it is a linking field.
|
||||
|
||||
This same issue can occur with text fields that contain a date or date and time only or "true" or "false" etc.
|
||||
|
||||
### Maximum file size
|
||||
|
||||
The actual limit on how many records can be imported / updated at once depends on many different things from individual browser limits, memory available, intermediate networking device and server configuration etc making it impossible to specify a limit.
|
||||
@@ -172,6 +184,7 @@ Each object type listed below links to a page showing the specific format requir
|
||||
- ##### [Head offices](adm-import-headoffice.md)
|
||||
- ##### [Parts](adm-import-part.md)
|
||||
- ##### [Part assemblies](adm-import-part-assembly.md)
|
||||
- ##### [Part inventory](adm-import-inventory.md)
|
||||
- ##### [Part warhouses](adm-import-part-warehouse.md)
|
||||
- ##### [Projects](adm-import-projects.md)
|
||||
- ##### [Service rates](adm-import-service-rate.md)
|
||||
|
||||
Reference in New Issue
Block a user