Task #534
open
Make correlation attribute non-mandatory
0%
Description
Sometimes, we just don't require correlation.
Updated by Alena Peterová over 6 years ago
- Priority changed from Low to Normal
Increasing the priority a bit, because it slowed me down a bit just now :-)
I needed to use the reconciliation of contractual relationships without correlation, because there were collisions between IDs of contracts and IDs of organizations. The synchronization tried to match contracts by searching in organizations. As a workaround, I had to create a new attribute in the schema and use it for the correlation attribute. If the attribute wasn't required, everything would be easier.
Updated by Alena Peterová over 6 years ago
Alena Peterová wrote:
I needed to use the reconciliation of contractual relationships without correlation, because there were collisions between IDs of contracts and IDs of organizations. The synchronization tried to match contracts by searching in organizations.
It turned out that the synchronization contractual relationships doesn't support correlation by any special attribute. So the correlation found all contracts, this resulted in the message as in #475 and spoiled everything.
So the correlation attribute should definitely be non-mandatory :-)
Updated by Vít Švanda over 6 years ago
Synchronization contractual relationships supports correlation by contract name attribute.
Updated by Marcel Poul about 6 years ago
I also cannot see, why the sync tolen must be mandatory. For the situation, where it is used, it just can skip the operation or print warning.
Updated by Alena Peterová almost 6 years ago
- Priority changed from Normal to High
Please make the correlation attribute (and so computing the state "Not Linked") non-mandatory. We have several use cases where we don't want to use correlation. Maybe it could make the synchronization faster without correlation.