🗺 Source Format Mapping Destinations
Dataset > Standard Query Library > Upload Dataset Destinations has a machine-generated version of this that's much more comprehensive.
|
Scope |
Mapping Destination Name |
UI Name and Location |
Name in CJ |
Database Location/XML Name |
Note |
|---|---|---|---|---|---|
|
|
Record > Slate User Login Override |
SSO Username in Profile > Edit Slate ID |
SSO Username |
|
|
|
|
Record > Slate ID Matching Only |
|
|
ref_matching |
Matched against Person Reference ID. |
|
|
Application Fields > App: Created Date |
|
Created Date |
|
Only imports during application creation; cannot update existing app's creation date. |
|
Users |
Account > User ID |
Edit User > User ID |
Username |
|
|
|
Dataset |
Record > Row Slate GUID Matching Only |
|
|
|
|
|
Dataset |
[Entity Name] > GUID (Matching Only) |
|
|
|
|
When importing to an Application-scoped Entity, a static mapping of "App: Round Use Existing = Yes" will create entities on the Rank 1 application.
When using a "Unique for Merging" free text field for matching, make sure your values do not exceed 64 characters or they will be unmatched.
No Comments