Every entity has it own set of predefined fields, which are documented per entity in their file definition. But there are some common fields that will be found in many entities.
File based import and Plankton
These fields can be found in both the file based import and the web API RESTful service.
Fields with Code as suffix; the unique key of the entity as known in the master data. See below for more information about keys/codes.
A unique internal/private name for the record of an entity; this identifies the entity in a human readable way; will not be displayed publicly
The Language Code Identifier. Defines the language and country of a record (ie. Product translation).
Records must be supplied for every language and country combination your application will be available in. Even if the data is the same for a language in multiple countries.
The most common values:
(Google 'LCID' for complete list)
Data that can not be placed in the predefined fields can be placed inside XML in this field.
<root><htmlvalue>value <with html></htmlvalue><anotherfield>1</anotherfield></root>
See Misc XML, but formatted as JSON.
The two-letter ALPHA-2 ISO 3166 notation of the country code.
File based imported only
The fields are specific for the file based import
ID that indicates the type.
Latitude and longitude of a location.
About unique keys - code fields
If master data does not have a unique key or the key consists of multiple fields, a single key must be created by joining fields together to create a unique key. To ensure a unique key is created out of multiple fields, a common technique is to use a separator between the fields, ie. pipe symbol (ASCII 124).
An example for a shipping address of a customer. The key for the customer is 'CC654'. The shipping address does not have a unique key, but is unique for the customer as '001'. The shipping address key would be 'CC654|001'.
Keys must be unique in a single file.