Autogenerated IDs for crosswalks
Learn about autogenerated IDs for crosswalks representing different data sources.
For crosswalks, the behavior depends on whether the value was sent.
Value was Sent | Reaction |
---|---|
No | Generate a new crosswalk value |
Yes | Use the crosswalk value that was sent |
Simple and Nested Configurations
{
"uri":"configuration",
"schemaVersion":"1",
"referenceConfigurationURI":"configuration/_vertical/life-sciences",
"entityTypes":[
{
"uri":"configuration/entityTypes/Object",
"label":"Object",
"description":"Object",
"uniqueGeneratedValuePerEntityPerRequest":true,
"attributes":[
{
"uri":"configuration/entityTypes/Object/attributes/AutoGeneratedSimple",
"name":"AutoGeneratedSimple",
"label":"Auto-generated Simple",
"type":"String",
"autoGenerated":true,
"generateIfEmpty":true,
"generatedValueUniqueForCrosswalk":true,
"generator":"UUID4_generator",
"autoGenerationPattern":"Simple_{value}"
},
{
"uri":"configuration/entityTypes/Object/attributes/AutoGeneratedNested",
"name":"AutoGeneratedNested",
"label":"Auto-generated Nested",
"type":"Nested",
"autoGenerated":true,
"generateIfEmpty":true,
"generatedValueUniqueForCrosswalk":true,
"generator":"UUID4_generator",
"autoGenerationNestedPattern":{
"Type":"AUTO",
"ID":"{value}"
},
"attributes":[
{
"uri":"configuration/entityTypes/Object/attributes/AutoGeneratedForcedNested/attributes/Type",
"name":"Type",
"label":"Type",
"type":"String",
"description":""
},
{
"uri":"configuration/entityTypes/Object/attributes/AutoGeneratedForcedNested/attributes/ID",
"name":"ID",
"label":"ID",
"type":"String",
"description":""
}
]
}
]
}
],
"sources":[
{
"uri":"configuration/sources/Auto",
"abbreviation":"Auto",
"label":"Auto",
"autoGenerated":true,
"generator":"UUID4_generator",
"autoGenerationPattern":"Source_{value}"
}
]
}
Here are examples of how simple and nested auto-generated IDs look in the in the user interface.
Simple
autoGenerationPattern
to prepend the string "Simple" to
the random string.Nested
SEQUENTIAL Configuration
{
"name": "Sequential",
"type": "SEQUENTIAL",
"rangeStart": 12,
"step": 3
}
Reltio Data Cloud doesn't check if the generated value doesn't overlap the existing attribute/crosswalk values which were not produced by the generator, The only way to make sure that there won't be any conflicts with existing IDs is to analyze existing values and configure appropriate generation pattern and — in the case of the SEQUENTIAL generator — starting value and increment.