Skip to content

Update SFMC doc to clarify field creation [DOC-339] #2002

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 12, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -287,7 +287,7 @@ Personas sends audience membership and computed trait values to SFMC using Ident
When you sync to an existing Data Extension, note these additional requirements:
- The table cannot have an existing **Primary Key**, unless it is the `Contact Key` field, and the field type is `Text`.
- All fields in the Data Extension must be nullable (meaning optional, or not required), except the `Contact Key` field.
- Any fields that you send with Segment, and which already exist in the Data Extension, must be of the correct data type. If they do not exist, Segment creates them for you. The standard identifiers Segment sends come from the [Context object](https://segment.com/docs/connections/spec/common/#context), and appear in the image below.
- Any fields that you send with Segment, and which already exist in the Data Extension, must be of the correct data type. The standard identifiers Segment sends come from the [Context object](https://segment.com/docs/connections/spec/common/#context), and appear in the image below.

![](images/existing-dext-data-types.png)

Expand Down