Import - Creating a New Entity or Customizing an Existing Entity

This topic provides high-level steps to change or enhance the default import framework.

Warning: It is recommended to make changes or enhance the import framework only after being completely aware of the implications of attempting such a change.

Steps to Edit the Default Import Framework

  1. Copy the flow that includes the required logic and then edit the copied flow instead of editing logic in the default flow. That way, the original flow with its default functionality will be available if the copied flow needs to be discarded.
  2. Edit and / or include new integration mapping records.
    OR
    If you are customizing the entity by adding a new field, create the integration mapping record for the field.
  3. Create logic in the copied flows to manage entity creation, entity updates, and duplicate checks (if required).
  4. If the value of a source field requires special handling in a different custom flow, create logic in the copied flow to pass the parameter to the custom flow, and also include logic to consume the parameter after its processed in the custom flow.

Steps to Skip Entity Creation

A framework is available in the Contact entity where the creation of a specific related Test Score record can be omitted. To do so, create the following Integration Mapping record:

  1. Type the following values in the Parameters field:

    {Name of the column},<Value>,False.

    • {Name of the column} – the external field name of the column that must be skipped.
    • <Value>
    • False or True – set it to false to ignore the entry.
  2. In the Record Type field, set the following value:

    <Parent entity>.<Related Entity>.<Nth record>

    Where:

    <Parent entity> - Type the display name of the parent entity, in this case the contact entity.

    <Related entity> - Type the display name of the Test Score entity.

    <Nth record> - type the instance of the Test Score record that must be omitted. For example, 2 or 3.

    Example: Text in this field can be Contact.TestScore.1

  3. In the Internal Field Name field, the value must be IsTestScoreValidRecord.
  4. In the Template Type field, select the applicable Test type.

Steps to Append or Overwrite Multi-Select Values

A framework is available in the Contact entity for appending or overwriting multi-select field values when they are imported.

To do so, create an Integration Mapping record for a multi-select field (e.g. Race, Contact type) and configure the following field:

  • Reset Multi Select Value - Set one of the following values in this field:

    • No - Indicates new values will be appended to the existing saved values. It is the default value.

    • Yes - Indicates existing values will be replaced with new values.