Thank you for sharing the details. I am not sure if uppercase of lowercase will cause an issue but i had seen issue where this casing difference was showing me warnings, so probably it could be the issue.
Can you please try to make sure that new ac parent value is exactly the same without the differences between uppercase and lowercase and then try to trigger the operation.
Hi @vguleria, yes we are still getting the error and already we have set “AC_NewParent” without the differences between uppercase and lowercase long time ago.
I think then it would be wiser to check the issue with sailPoint support team. They can access the logs generated by the cloud rule and then should be able you further.
Unfortunately, i can not think of anything else here which might have caused an issue. Perhaps, May be a last attempt when i checked the error message again , it is trying to update the user
CN=Test,OU=Departed,OU=User Accounts,DC=Test,DC=Test,DC=com
Not sure but you can double check DC=Test,DC=Test if this is correct. But having said that i believe you can have a look at the issue with support team and they should be able to access the logs and provide you the proper resolutions.
Try doing thing in two steps, first Move the account and create a lifecycleState just for that. This will trigger the Native Change and update the link on IDN. Them create the Leaverr/terminated state to do the other operations.
I am also facing same issue. We are updating AC_newParent attribute through before Provisioning rule, account is getting updated in AD properly. but we are getting sailpoint.connector.ObjectNotFoundException exception in events.
Please let me know the solution if you are able to resolve this issue.