admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2022-03-29 18:23:04 +00:00
parent f745c8a76a
commit 4d9b17d17a
2 changed files with 3 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/8.0/ayanova/docs/adm-import-inventory.md
View File

@@ -10,6 +10,7 @@ Inventory transactions can only be imported, not updated.
## Required fields
- Description (if left empty the [import Tag](adm-import.md#import-items-are-automatically-tagged) is used)
- PartViz (Must match name of existing Part)
- PartWarehouseViz (Must match name of existing Part warehouse)
- Quantity

14
docs/8.0/ayanova/docs/adm-import.md
View File

@@ -106,9 +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 and there is no possibility of mis-interpreting the type of data in each field.
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 less 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).
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.
### Import file format
@@ -146,16 +146,6 @@ 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.