0
edits
Changes
no edit summary
===Setting the File Properties===
The File Type can be a CSV,Text file, an XML file or , Fixed Length, or JSON data.
The File Encoding can be UTF-8, UTF-16 or ANSI. This option is hidden if the File Type is XML.
:* If more than 100 fields are required, then you will need to create two upload files.
* Ignore Lines - You can specify the number of rows to ignore from the beginning of the file. This can be used to ignore column headers, if they exist as the first row in any file.
* Field Delimiter - drop-down list showing the delimiter options used to separate different values in the file into different columns. Will not be presented when the File Type is XMLor JSON.
* Use HTML Table - An HTML table is very useful where imported data contains multiple records and a single record set of fields exists within SmartSimple. For example, if you wished to import multiple lines of sales information into a single text box field you would enable the HTML table feature and then map all the fields into a single field indicating the column and row delimiters. Will not be presented when the File Type is XML.
* Column Delimiter - free text field to allow entry of any delimiters required to separate different values in the file into different columns. Will not be presented when the File Type is XMLor JSON. * Row Delimiter - free text field to allow entry of any delimiters required to separate different values in the file into different rows. Will not be presented when the File Type is XMLor JSON.
* Record Node Name - Only presented when the File Type is XML.
* Record Node Filter - Only presented when the File Type is XML.
* The field name is selected from the Field combo box.
* In order for the update to succeed, a single field is required to match an upload record to an existing database record this is indicated as the Identifier field. Customer data will generally be an account number type field.
* The Table header field is only required if you are using the HTML Table feature or when loading an XML or JSON file.
* The '''Duplicate Match Beahviour''' drop-down allows user to specify the behaviour whenever multiple records are matched using the Identifier field(s).
:* Update Unique Match Only - will only update when one matching record is found
==Important note about XML Files==
If the contents of any the elements in an XML file being autoloaded contains certain special characters it will disrupt the XML structure, making the message unreadable by the receiving server. The l'''ess less than''' symbol (<) and '''ampersand''' (&) are two primary special characters to be concerned about. When including fields that may contain those characters you should use a special wrapper so the receiving understands that they are data content and not part of the XML structure:
:<font size="2"><![CDATA[ '''''CONTENTS''''' ]]></font>
* It is advisable to use CDATA for any field containing text since the contents are often unpredictable.
==Note about JSON Files==
JSON format should start with a '''data''' node, as shown in the example below
<pre>
{
"data":[{
"Name":"Acme Corporation",
"Phone":"416-123-4567",
"CompanyID":"496246"
},
{
"Name":"Super Banana Ltd.",
"Phone":"800-555-1234",
"CompanyID":"496244"
},
{
"Name":"Red Apple Supply",
"Phone":"917-123-0000",
"CompanyID":"496248"
},
{
"Name":"Orange you Glad",
"Phone":"410-222-2030",
"CompanyID":"496242"
}
]
}
</pre>
==Ad hoc upload url==