Skip to main content

Import - What are generic import data field header columns?

The column(s) following the Command Action column are known as Data Field Header Columns and must contain the Equus Platform Unique Name of the field which will be populated by data in this column. T

Updated over 2 weeks ago

The column(s) following the Command Action column are known as Data Field Header Columns and must contain the Equus Platform Unique Name of the field which will be populated by data in this column.

Generic_Import_Header_columns.png

The Unique Name is always expressed in the format TABLE_NAME!FIELD_NAME. The most common way to identify this value is to look at individual fields on the Assignment Pro's screens in Data Dictionary Override mode.

In addition to Unique Name, data field header columns can contain one or more of the following attributes:

  • recordIdentifier=True - This property is similar to a "filter" that allows you to narrow down which data gets updated. The table affected by this is the first segment of the Unique Name in the column (i.e. TABLE_NAME!FIELD_NAME). For Update/UpdateOne/Upsert/UpsertOne rows, one or more fields for each table must be marked as recordIdentifier=True. These will be used as key fields by the import engine when determining which row to update. This attribute can only be ignored for Insert command rows but must be included for Update/UpdateOne/Upsert/UpsertOne rows to avoid unintentionally updating multiple records.

  • lookupValue={somevalue} - This flag indicates if the value being entered on the import file should be the name/value the user sees or what is saved in the database (the CLASSIFICATION table 6 character code). The lookupValue = TRUE is the default mode so no need to add it to all fields.

  • lookupSource={somevalue} - This property is rarely used. It indicates the specific source for a field when performing a lookup that can be against multiple sources. An example is Company Segments. Using lookupSource=Code allow you to use the segment code instead of the ID or Display Value.

Things to Note

  • Not all Data Field Header Columns need to use one of the above attributes after the Unique Name.

  • The Data Field Header Columns should be grouped together by Table. For example, all RESOURCE fields should be added, then all RESOURCE_CF fields should be added, etc. Not doing this may result with errors when importing records.

Did this answer your question?