Defect #2424
closed
Synchronization creates a new identity with the default value in EAV instead of the mapped value
100%
Description
Version 10.4.1
When synchronization of identities creates a new identity and some of the mapped EAVs have default value, then the default value is saved in the identity, instead of the mapped value.
The second run of the synchronization updates the identity correctly.
- Create an EAV of IdmIdentity with some default value - "false" in our case.
- Map the EAV in the synchronization of identities, set "Transformation from" to some different value - Boolean.TRUE in our case
- Run the synchronization
- Identity was created, but the value of the EAV is "false". (wrong)
- Run the synchronization again
- The EAV was changed to "true". (OK)
(Our use case: We want to "flag" identities created by one special synchronization as "System accounts". By default, the identities are not system accounts.)
Tested for Boolean and ShortText, the result is the same.
Files
Related issues
Updated by Alena Peterová over 4 years ago
- Subject changed from Synchronization of identities creates a new identity with the default value in EAV instead of the mapped value to Synchronization a new identity with the default value in EAV instead of the mapped value
- Description updated (diff)
Updated by Alena Peterová over 4 years ago
- Subject changed from Synchronization a new identity with the default value in EAV instead of the mapped value to Synchronization creates a new identity with the default value in EAV instead of the mapped value
Updated by Radek Tomiška over 4 years ago
- Related to Task #2248: Synchronization: save extended attribute values together with entity added
Updated by Vít Švanda over 4 years ago
- Status changed from In Progress to Needs feedback
- Assignee changed from Vít Švanda to Radek Tomiška
I found the problem. If new entity is created by sync, default EAV values are created by generators and added to the entity as IdmFormInstance. This form instance contains only default values in this moment. After that EAVs attributes are updated by sync and with new transformed values (calls directly the form-service). After that original instance of entity is publised with IdmFormInstance contains default values. This update causes the problem, because attribute is updated by default value again.
This issue will be fixed within #2248 where an attributes will saved together with entity.
Updated by Radek Tomiška over 4 years ago
- Related to Task #1267: Support save EAV with Entity added
Updated by Radek Tomiška over 4 years ago
- Status changed from Needs feedback to Closed
- Assignee changed from Radek Tomiška to Vít Švanda
- % Done changed from 0 to 100
- Affected versions Morganite (9.2.0), Morganite (9.2.1), Morganite (9.2.2), Onyx (9.3.0), Onyx (9.3.1), Opal (9.4.0-rc.1), Onyx (9.3.2), Onyx (9.3.3), Opal (9.4.0-rc.2), Onyx (9.3.4), Opal (9.4.0), Pyrite (9.5.0), Pyrite (9.5.1), Pyrite (9.5.2), Pyrite (9.5.3), Pyrite (9.5.4), Quartz (9.6.0), Quartz (9.6.1), Quartz (9.6.2), Quartz (9.6.3), Quartz (9.6.4), Quartz (9.6.5), Pyrite (9.5.1.2), Quartz (9.6.6), Rhyolite (9.7.0), Rhyolite (9.7.2), Rhyolite (9.7.3), Rhyolite (9.7.4), Rhyolite (9.7.5), Rhyolite (9.7.6), Rhyolite (9.7.7), Rhyolite (9.7.8), Rhyolite (9.7.9), Rhyolite (9.7.10), Rhyolite (9.7.11), Rhyolite (9.7.12), Rhyolite (9.7.13), 10.0.0, Rhyolite (9.7.14), 10.0.1, 10.1.0, Rhyolite (9.7.15), Rhyolite (9.7.16), 10.2.0, 10.0.2, 10.3.0, 10.3.1, 10.3.2, Rhyolite (9.7.17), 10.3.3, 10.4.0, 10.4.2, 10.4.3, 10.4.4 added
I did test, it works, thx!