Difference between revisions of "Usermanual/ImportCSV"
old>Admin (Created page with 'The import function allows selected users to upload data, for either creation of new or update of existing records. All normal restrictions are in place, so there will be no dif…') |
m (8 revisions imported) |
||
| (7 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
The import function allows selected users to upload data, for either creation of new or update of existing records. | The import function allows selected users to upload data, for either creation of new or update of existing records. | ||
All normal restrictions are in place, so there will be no difference between imported and manually | == Using import == | ||
All normal restrictions are in place, so there will be no difference between imported and data entered manually through regular forms. | |||
During import each line in the import file is handled as a seperate job. Consequently some lines may fail and some lines may succed: The results can be retrived after the import where a modified version of the import file including the succes/failure status information, will be returned to the user. | During import each line in the import file is handled as a seperate job. Consequently some lines may fail and some lines may succed: The results can be retrived after the import where a modified version of the import file including the succes/failure status information, will be returned to the user. This file makes it easy to error correct, as the the format is exactly the same as the import file. | ||
== Import format == | |||
Import files must apply to the following restrictions | |||
* File content is in '''CSV format''' | |||
* Column names should use the field '''system name'''. | |||
The easiest way to build a working import template, is making a [[Usermanual/ExportXL|XL file export]] with the "System export" option enabled. | |||
== Options == | |||
Imports can have certain options included that change what happens during the import | Imports can have certain options included that change what happens during the import | ||
* | * Continue on errors: Do not stop processing on single field errors | ||
* | * Ignore empty values: Empty values are never processed (default: treat as "" or null) | ||
* | * Disable codeunits: Disable custom functionality | ||
* Disable validation: Disable field restrictions | |||
Warning: Do not use the last two options (codeunit/validation), unless you 100% certain how the solution works. | |||
== Enabling user profiles == | |||
Add the role data handler for the users that should be allowed to import data | |||
Designer > Users > Edit users > [USER] > "Data handler" | |||
Latest revision as of 11:56, 10 December 2021
The import function allows selected users to upload data, for either creation of new or update of existing records.
Using import
All normal restrictions are in place, so there will be no difference between imported and data entered manually through regular forms.
During import each line in the import file is handled as a seperate job. Consequently some lines may fail and some lines may succed: The results can be retrived after the import where a modified version of the import file including the succes/failure status information, will be returned to the user. This file makes it easy to error correct, as the the format is exactly the same as the import file.
Import format
Import files must apply to the following restrictions
- File content is in CSV format
- Column names should use the field system name.
The easiest way to build a working import template, is making a XL file export with the "System export" option enabled.
Options
Imports can have certain options included that change what happens during the import
- Continue on errors: Do not stop processing on single field errors
- Ignore empty values: Empty values are never processed (default: treat as "" or null)
- Disable codeunits: Disable custom functionality
- Disable validation: Disable field restrictions
Warning: Do not use the last two options (codeunit/validation), unless you 100% certain how the solution works.
Enabling user profiles
Add the role data handler for the users that should be allowed to import data
Designer > Users > Edit users > [USER] > "Data handler"