...
This asset reference also appears in the Confirmation.csv file generated by the import and in the Asset Bulk Export .csv file. Either of these files may be useful to update the matching asset details in other systems, and then they can be included in your new import file when the assets change. Gruntify will match up the Asset IDs and will indicate that you are updating a record rather than adding a new record.
Mapping Fields
The key screen in the import is the Mapping screen.
The first column "Destination Control Header", is a list of the basic Asset fields such as Customer Asset ID, and the labels from the controls in the selected Asset form. The Asset form entries are at the bottom of the list.
The second column “Source File Column Header” is the field or column name in the import file. The “Source File Row Data” is the first three entries from the file, shown beside as a sample of the data.
...
The general mapping rules are:
The Asset Status values should be either "Active" or "Disabled". If you do not have a value in your import file for status, leave the entry blank and it will default to "Active".
Match each Control Header with a Column Header where the import file contains the appropriate data for that Control.
If there isn’t a matching entry in the import file and the header field is not mandatory, then that field will be left blank in a new asset, or not updated in an existing asset.
If there isn’t a matching entry in the import file but the header field is required (shown with an asterisk), then any default value given for this field in the form will be be used in a new asset. If updating, leave it unmapped and the field will not be updated.
If there isn’t a matching entry in the import file but the header field is required but no default value exists then an error will occur in creating a new asset. This may happen for a File field or a Media field as they do not have default values.
Related Articles
Filter by label (Content by label) | ||||||||
---|---|---|---|---|---|---|---|---|
|
...