we have a requirement for attribute synchronization for previous data the attribute sync should not happen it should happen only for new users . when i am enabling attribute sync it is synching to previous data also that we dont want
1 Like
Hi Chaithanya,
You can consider updating your identity profiles with a firstValid transform to first take the value from the existing account, and then if not present generating it from identity attributes. Otherwise, it will sync by default.
Thanks,
Margo
1 Like
the issue is in ad we have previous data
that should not sync only new user need sync
@sharvari , @jesvin90 , @mcheek , @kjakubiak , @enistri_devo , @KRM7
@iamnithesh can you reply
This is the standard attribute sync behavior.
To update a subset of users you can try to use an Update Account Profile on the source configuration and for each attribute being set, check the conditions before setting a new value. This isn’t a best approach performance wise but a workaround.
Another option could be using sync along with a Before Provisioning Rule. In the rule for modify operation check if the user is old or new and based on that make changes to your provisioning plan.
i just modified the transforms
You can do this using Transform as well.
- Get Link (AD Account) created date
- Create separate Identity attributes for AD account
- If AD account created before a specific date then its old account, if it is old account AD Identity attribute will have data from existing AD account, if it is new account then AD Identity attribute will have data from HR account
- If the AD Identity attribute and account attribute is different then only attribute sync will trigger
2 Likes
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.