Each time we aggregate, another entry is made for some fields. Not all fields are affected.
For example:
Gender: F
F
F
(another F will be added after each aggregation).
Affected fields: Application name, Gender, Cellphone, employeenumberinternal and workphone.
Example of fields that are NOT affected - department, division, status.
Most fields are set to string and entitlements and groups are set to multivalued.
We’ve checked on SCIM and they see the data only once and it’s not being sent in duplicate. Also, it increases every time we aggregate. It’s a new authoritative source.
Hi @mvanderberg, it’s not normal but anyways you can try sth like the below then let us know what the result is.
A. Review the Application Schema and ensure that affected attributes (e.g., Gender, Cellphone) are not marked as multi-valued. They should be configured as single-valued strings.
B. If using a pre-parse rule or custom aggregation logic, verify that you’re not wrapping attribute values in lists or arrays. Use plain strings for single-valued attributes.
C. If these application attributes are mapped to identity attributes, ensure that the identity mappings are also defined as single-valued to prevent accumulation.
D. Clean up existing duplicate values from previously affected accounts using a cleanup rule or script to reset attributes to their correct form.