Relationship Crosswalk Consolidation task
Learn more about the api to consolidate relationship crosswalks.
This task enables you to manage relationship data by consolidating relationship crosswalks, ensuring the most recent crosswalk from the same contributor is retained. This is based on a similar relationship type, start/end object contributors, and/or source type. For example, for the HasAddress relationship type, multiple crosswalk entries are provided by the same contributor. In this case, consolidation ensures that the most recent entry is retained when crosswalks are consolidated.
The contributorCrosswalkSingleSourceUpdateMode flag determines if the consolidation is done based on tenant-level or relationship level. For more information about this flag, see topic Consolidating relationship crosswalks.
Requests
POST {ApplicationURL}/api/{tenantId}/consolidateRelationsCrosswalks| Parameter | Required | Description |
|---|---|---|
| tenantId | Yes | ID of the tenant to check. |
| distributed | No |
If set to
true, the task runs in distributed mode. Default value is false. For more information, see Distributed mode. |
| taskPartsCount | No |
Specifies the maximum number of sub-tasks for distributed execution. The platform determines the optimal number based on performance limits. Default value is
2. Note: This parameter is only applicable when distributed=true. Otherwise, it s ignored. |
| fixInconsistency | No |
The task does not fix a found inconsistency if this parameter is set to Default is |
| produceEvents | No | Determines if changes to the relations must cascade to entities. Default is false. |
Body (optional)
Provide a JSON array that lists the entity and/or relationship URIs to validate.
Example:
[
"reltaions/Uri1",
"reltaions/Uri2",
...
"reltaions/UriN"
]