@Snehamani what is the reason why it failed .It can fail due to uniqueness also.
Please elaborate the issue description
Thanks
Shantanu
Hi @Snehamani ,
Welcome to Sailpoint Developer Community!
Please share error message or screenshots, why it failed
@Snehamani Can you please check the error? It can fail due to multiple reasons.
Hi @Snehamani ,
If you have remove account from identity then after next aggregation the account again tagged with same account due to correlation and remove operation will not delete from target application.
Best way to check is configure the RBAC criteria or add identity directly to that role.
Thank you.
Did you remove the account from SailPoint? If the account is removed from SailPoint, the account still exists in the target application hence the provisioning will likely fail
4 Likes
It says account with the username or name already exists. So, it cannot create a new user with the same name.
Try creating a new user with different name.
1 Like
Hi @Snehamani ,
This is happening because in your create account mapping there is no unique counter added. Due to duplicate account you are facing error. Try to add unique counter in create account profile for unique attribute.
1 Like
Yes I removed the account from the identity
As Suraj mentioned, you can add counter, else remove the account from the target source and try provisioning (if is for testing)
2 Likes
Hi @Snehamani ,
can you go to search and check account activity for the user and check what values it is passing in provisioning plan for create operation ?
Hi @Snehamani ,
Which connector you are using ? Also share account activity screenshot by masking sensitive data. Above screenshot for events.
I’m using service now connector
Your create profile looks good. Are you facing same error with other identities as well?
Are you trying to create an account with null values?