Hi All,
We have set up Attribute sync for some AD attributes we want to change based on HR data (Job Title and Location)
During the HR data import the Attribute changes are triggered and a CR raised but AFX fails with an error
See attached for details on error and settings
Any thoughts?
Thanks in advance,
John
Hi Boris,
Thanks for your reply.
The screens you required are below
It constantly fails at the moment. I have tested using Job Title and Location - in both instances the CR fails with the same "attribute mapping" error
When putting the connector into test we can make the changes in the target system
Kind regards,
Configuration seems to be ok.
Can you share the export of fulfillment workflow which is configured to perform attribute sync?
The only strange thing is that the account seems to be not associated to any user (screenshot below).
Is this an orphan account?
Also, what product version?
Hey Boris,
I also noticed this case > Relate User to Attribute Sync
This seems to relate to the user/account issue with the Attribute Sync but has no responses as yet
The account is not an orphan. Product Version - 7.0.2 PO3
I have a copy of the workflow to share but cant seem to attach it to this case - we are using the same workflow we do for AD Fulfilment (with Att Sync now enabled in the workflow)
we have 2 domains at the moment. I configured this for both AD targets but the same error is presented.
The workflow for each domain is slightly different - in Domain A users lived in different OU's dependant on department (nightmare for us)
The other domain - Domain B has all users in 1 OU so the workflow for each is slightly different - B has a lot of logic removed that isn't required to calculate OUs etc.
In both cases the CR Fails because a command parameter mapping cannot be found for the attribute
Was this issue ever resolved? I see no solution listed.
What product version?
Can you share a screenshot from the Update an Account capability while in Edit mode?
Is it constantly failing or you have some scenarios where it's successful?
When you are testing connector capabilities, are you able to update the location (physicalDeliveryOfficeName attribute) successfully?
Can you share additional screenshots from the created change request? (similar to the screenshot below)