Skip to main content
Version: 6.18 (draft)

Contact output

This plug-in can be us ed in transformations to import contacts into ConSol CM.

The following settings are available:

  • Step name: Specify the name of the transformation step. The default name is the name of the plug-in.

  • Customer group: Select the customer group of the contacts.

  • Batch size: Specify how much data should be imported in one step.

  • Contact object for CM/Track profile: Select the contact object to which the CM/Track user profile will be assigned. This value is optional.

  • Input field with CM/Track username: Select the field which contains the name of the CM/Track user profile.

  • Default value for CM/Track username: Enter the name of the CM/Track user profile which should be used if no CM/Track user profiles are included in the data or the Input field with CM/Track username field is empty. This value is optional.

  • Do not remove existing CM/Track profile assignment if input field is empty: If this option is selected, the CM/Track user profile which is assigned to the contact is not removed if the Input field with CM/Track username is empty.

  • Name of the contact ID field:: Enter the name of the new field which will include the contact ID. The ID can be used in the following transformation steps for additional processing. This value is optional.

  • Input field: This column can include all fields of the previous transformation step. These fields are mapped to the contact fields in ConSol CM. Click Get fields to load the current input fields.

  • Contact object: Select the contact object which the field belongs to. This is usually either the company or the person of the contact data model.

  • Contact field Select the contact field which should be mapped to the input field. Syntax: <field group>:<field> The field Unit:Deactivated can be used to indicate if the contact is deactivated (true) or active (false).

  • Operation type: Specifies how the fields should be processed. All fields must have the same type. The available options are:

    • Create or error: A field of this type is only created, but not updated.

    • Update or error: A field of this type is only updated, but not created.

    • Fetch or error: A field of this type is only used for selection, but it is not created or updated. This works only for existing contacts. An exception is thrown if the contact is not found. The selected contact can be used in the following transformation steps for additional processing.

    • Create or update A field of this type is created (if the contact is not found), or updated (if the contact is found).

    • Create or fetch A field of this type is only used for selection (if the contact is found), or creation (if the contact is not found), but not for update. The selected contact can be used in the following transformation steps for additional processing.

  • Search criterion: Possible values are true and false. The value true means that the contact field is used to find an already existing contact with the same data. All fields marked with true are used together for this search, therefore they should describe the unique key of a contact.

  • Search case insensitive Specify if the search should be case-sensitive (false) or not (true).

info

If the contacts, which you want to import, include data fields of the types List or Columns, you need to use the Contact container field output to import these fields. To import comments or attachments, use the Contact content output plugin.

warning

The following behavior should be considered when importing contact data:

  • If you create contacts in a two-level contact data model where the company is mandatory, the input file has to include the ID of the company which the person belongs to. The ID has to be mapped to the contact field of the data type Contact reference. If you do not know the company ID, you can use to Contact ID lookup plugin to retrieve it. The ID needs to be merged to the input file.
  • If you update data fields of existing contacts, all the contact fields which are mapped to input fields are overwritten. This means that existing field values are lost if the corresponding field has an empty value in the input file. If you want to maintain such values, you need to retrieve them using the Contact input plug-in before and merge them with the values from the input file.
  • If the fields which constitute the search criterion are not unique, e.g. more than one matching contacts is found, a new contact is created instead of updating the existing one.