Print this page

"Error binding data bound member" in Contact Builder

Knowledge Article Number 000220546
The message, "Error binding data bound member," means that a Contact key record could not be found in the Contacts framework. Learn some common causes for this error and resolutions, below. 

Channel Address field missing from Channel Address Order

The Channel Address Order determines the order of priority for all sendable address fields contained in root Attribute Sets linked to Attribute Groups in Data Designer.  For example, if a contact key is present in multiple sources with different email addresses, the Channel Address Order will determine to which of those email addresses a message will be sent.

If a Contact Key is evaluated by Contacts that exists in a root Attribute Set that is not configured in the Channel Address Order, then the default address cannot be found, and the message Error Binding Data Bound Member will be returned.

Follow the steps below for each Attribute Group in Contact Builder to confirm if a channel address field in a root data extension is missing from the Channel Address Order.

1. Go to Contact Builder | Data Designer.
2. Click Attribute Group.
3. You will receive the notification, "Changing Contact data can impact your account configuration."  Review the message, then click Ok.  
NOTE - It is recommended to view the data in the Attribute Group only; changes can potentially have a negative affect on objects in the account relying on the data present in the Attribute Group.
4. Click on the Relationship link for the first Attribute Set.
5. Check the right-hand side of the relationship. If the drop-down says "One," then confirm if the "Use as Root" box is checked.

  • If yes, note the Data Extension name and field name for the Channel Address field present in the list of attributes.  A Channel Address is a field with an Email Address data type (showing an icon with the @ character), a Phone data type (showing an icon that looks like a telephone), or a Text data type for a push DeviceID.  Click Cancel to close the Link Data Extension wizard.
  • If no, click Cancel to close the Link Data Extension wizard, then continue to check each relationship link in the attribute group.

6. Repeat Steps 1-5 for each Attribute Group in the account.

Once you have the list of all Channel Addresses in Data Designer, confirm that these have all been added to the appropriate Channel Address Order.
1. Go to Contact Builder | Data Designer.
2. Under Email, compare the list of Channel  Addresses to the list of all Email Channel Addresses noted in step 5 from above.  If there are any Email Channel Addresses noted in step 5 that are missing from the list of Channel Addresses in the account, these will need to be added to the Channel Address Order.  Follow steps a-h below to add these addresses to the Order.

1. Under Email in the Channel Address Order, click Edit.
2. Click Add Address.
3. A list of all sendable Data Extensions linked to an Attribute Group in Data Designer will be listed. Click the name of the Data Extension. 
4. A list of all fields with an Email Address data type for that data extension will be listed.  Select the field you wish to add to the Order.
5. Repeat for all addresses you wish to add to the Channel Address Order.
6. Click Save.
7. Drag the addresses under the Email Channel Address Order into the order of priority as desired.
8. Click Save.

3. Repeat step 2 for Push and SMS addresses (if applicable).


Contact Key doesn't yet exist in the Contacts framework

The term "Contacts Framework" refers to the network of linked Attribute Groups that access data in Data Extensions, which ultimately build the single view of the customer.  In order for applications to successfully interact with Contacts, any Contacts evaluated must be present in the Contacts Framework. If a contact is not present in a root source linked to the Contacts Framework, the above error message will be returned upon evaluation.

Follow these steps to confirm if a Contact exists in the Contacts Framework:

1. Go to Contact Builder | All Contacts.
2. In the left-hand navigation, click Entire Population.
3. In the search bar, enter the Contact Key, then click the magnifying glass.

If there are no results returned for this Contact Key, then it doesn't exist in the Contacts Framework.  The Contact Key will need to be added to a root source in order to be processed by an application using Contacts.

promote demote