Not all CTM:People have a User record, a user record is only created if you provide a login name.
The changes in CTM:People are propagated to User form, but the change on User form are not propagated to CTM:Peolpe form.
If User was created, but, somehow, unintentionally deleted, I think you can try to recreate the user register:
If it doesn't work, I think the solution of deleting and trigger the AD integration job manually would be a good one.
Hope that helps
You can make some changes on the CTM:People Form for that user which will retrigger the workflow defined on Save and will write the user to User Form.
It was a user with login ID. As statted, he had access to MyIT...
Seems the only solution is to delete the user and retrigger the AD job.
As stated in my original posts, changes done on CTM:People did not trigger the creation of the user on the User form.
How about recreating the user profile.
- Clear the user from user_cache.
- Create a new profile for that particular User.
I have just had another interesting issue...
One user had a change in the user name in AD, that change was synched with the daily AD job to CTM:People but it was not synced to the User form.
I had to manually adjust the loginID on User to enable the user to access MyIT again.
As far as I understood, all changes on CTM:People should be reflected on User as long as the user has a loginID...or am I missing something?
Anybody seen something like this before?
1 of 1 people found this helpful
yes I have seen this before when directly modifying the People record via an API where the supporting workflow to "push" the value to the User form was not triggered.
You will need to turn on logging to see if it is a result of the way the record is created e.g. via a "Merge" that does not therefore trigger the supporting workflow, or another issue that means the workflow is not firing.
Thanks, I will have a look to see what is happening.