Usermanual/ImportCSV - Revision history

Tvi: 8 revisions imported

2021-12-10T10:56:00Z

8 revisions imported

← Older revision	Revision as of 12:56, 10 December 2021
(No difference)

old>Admin at 12:02, 10 April 2013

2013-04-10T12:02:07Z

← Older revision		Revision as of 14:02, 10 April 2013
Line 21:		Line 21:

	Warning: Do not use the last two options (codeunit/validation), unless you 100% certain how the solution works.		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"

old>Admin: /* Import format */

2013-04-10T12:00:04Z

Import format

← Older revision		Revision as of 14:00, 10 April 2013
Line 11:		Line 11:
	* Column names should use the field '''system name'''.		* 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.		The easiest way to build a working import template, is making a [[Usermanual/ExportXL\|XL file export]] with the "System export" option enabled.

	== Options ==		== Options ==

old>Admin: /* Import format */

2013-04-10T11:58:03Z

Import format

← Older revision		Revision as of 13:58, 10 April 2013
Line 7:		Line 7:

	== Import format ==		== Import format ==
	Import files ~~should be saved i~~ CSV format~~, and column~~ names should be the field system ~~names~~.		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 "~~Sytem~~ export" option enabled.		The easiest way to build a working import template, is making a XL file export with the "System export" option enabled.

	== Options ==		== Options ==

old>Admin: /* Import format */

2013-04-10T11:56:28Z

Import format

← Older revision		Revision as of 13:56, 10 April 2013
Line 7:		Line 7:

	== Import format ==		== Import format ==
	Import files should be saved i CSV format, and column names should be the field system names ~~(allthough a lookup is attempted if the field is not found)~~.		Import files should be saved i CSV format, and column names should be the field system names.

	The easiest way to build a working import template, is making a XL file export with the "Sytem export" option enabled.		The easiest way to build a working import template, is making a XL file export with the "Sytem export" option enabled.

old>Admin at 11:56, 10 April 2013

2013-04-10T11:56:15Z

← Older revision		Revision as of 13:56, 10 April 2013
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.

			== Using import ==
	All normal restrictions are in place, so there will be no difference between imported and data entered manually through regular forms.		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.		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 should be saved i CSV format, and column names should be the field system names (allthough a lookup is attempted if the field is not found).

			The easiest way to build a working import template, is making a XL file export with the "Sytem 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		* Continue on errors: Do not stop processing on single field errors

old>Admin at 11:53, 10 April 2013

2013-04-10T11:53:01Z

← Older revision		Revision as of 13:53, 10 April 2013
Line 3:		Line 3:
	All normal restrictions are in place, so there will be no difference between imported and data entered manually through regular forms.		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.

	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.

old>Admin at 11:46, 10 April 2013

2013-04-10T11:46:19Z

← Older revision		Revision as of 13:46, 10 April 2013
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 ~~entered data~~.		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.

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…'

2013-04-10T11:45:42Z

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…'

New page

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 entered data.

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.

Imports can have certain options included that change what happens during the import
*
*
*