Fields allow you to better organize how contact data is imported into Cadence. A field must be set up on the Fields page in order to be allowed in a data import. In addition to selecting which fields are allowable, you are also able to configure permissions for each field.
Note: Only Admin users are able to manage import fields.
This article will cover:
- Navigating the Fields page
- Adding/Deleting Fields
- Field-level permissions
After fields have been configured, they can be viewed on the Fields page by navigating to "Team Name" > Data Management > Fields. Shown as checkboxes, each field has a level of permissions that govern how the data can be used within the platform.
Note: If a native or FTP integration is enabled for your team, you will find Fields under the integration settings rather than under Data Management.
The StaffId/user assignment field is an optional system field that allows you to assign contacts to specific users in Cadence (more information here). If you begin supplying a StaffId with your contact data, please continue to supply that information each time you import a contact; if it is left out of your import file, the staff assignment will be cleared out.
If you only want to clear out the staff assignment for a specific contact, include the StaffId field in your import, but make it null/blank for that contact. If you would like to clear out the staff assignment for all contacts in your import, leave out the StaffId field entirely.
Adding a New Field or Editing an Existing Field
Clicking [ Add Field] will allow you to set up new fields that are allowed to be included in an import. You can also edit the names of existing fields (as long as you do not change the context of the data stored in the field).
To delete a field, navigate to the Fields page and click the dots to the right of the name of the field. Select Delete from the drop-down list.
Note that deleting a field may impact any segments that use the field as criteria.
The check box in the Required column makes the field required on every import. Note that this requirement means the field must be present in the header row of every import--it does not mean that the field needs to actually contain data.
The check box in the Mergeable column controls whether or not the data is able to be merged into a text message by users in the team.
Visible to Users
The check box in the Visible to Users column determines whether or not the field is visible to non-Admin users when viewing the contact record. If this box is unchecked, the data will only be visible to Admin users.