Step 2: Formatting and Mapping Data

For more on formatting and mapping specific fields, see the Mapping section of the Connectors reference documentation.

Formatting Data

Can I merge rows?

Yes; this is supported for items in list type fields that are exploded across multiple rows for the same entity.

In the connector settings, list-type fields can be set to append list items. Each row in the data set will be processed, and any items mapped to the list field will appear on the entity after any existing items.

If multiple rows have different values for the same field, the value present in the last row to be processed will be applied to the entity.

Note that the Run Results table will only show the final row that is processed. This means that even if the list field is correctly populated, only the final item added to the list will display in the Results table.

Mapping Data to Fields

Address

If a mapping to an Address field (e.g., Street, City, State/Region, etc.) is failing, here are some things to check:

• Is the address valid when added to the entity via Entity Edit?
• Is there a space that needs to be removed?
• Is the country code mapped in the data set? If not, does the country of the entity match the country of the account? (If not, the country code must be specified in the data set.)

Linked Accounts

Due to the complexity of the Linked Accounts field, updates to Linked Accounts are not supported via Connectors or entity templates.

Field Types

Entity Relationship

Mappings to entity relationship type fields must reference the entity ID of an existing entity. If the referenced entity ID does not exist in the Knowledge Graph, a warning will be shown.

Entities must be added to the Knowledge Graph in the correct order to populate entity relationships (e.g., to link Entity B to Entity A, Entity A must already exist in the Knowledge Graph in order for Entity B to reference its entity ID). Use the Linked Connector trigger to ensure that any connectors that may be adding entities to the Knowledge Graph are run in the appropriate sequence.

Option

If a mapping to an option type field is failing, check these items:

• You must provide the API name of the field. Navigate to Knowledge Graph > Configuration > Fields — the API name is located under the display name for each field.
• Confirm that the options you are trying to map already exist on the field. From Knowledge Graph > Configuration > Fields, click on the option field you want to map. See the Field Settings section and confirm that the options already exist under the Available Options.
• For any built-in fields that are not visible in the platform, refer to the API documentation for the Entities API: Create and view the same Response Schema.

Yes/No (boolean)

Valid boolean field inputs are below:

• TRUE , true
• FALSE , false