Please share any images or screenshots, if relevant.
Please share any other relevant files that may be required (for example, logs).
Exception while updating account.Url: https://<…>/groups, Message: 400 : Bad Request, HTTP Error Code: 400
Share all details related to your problem, including any error messages you may have received.
Created a web service connector with an Add Account with entitlement attributes in the same api call. However, the web service connector is still automatically calling the Add Entitlement Operation after Add Account operation is call causing the error Exception while updating account.Url: https://<…>/groups, Message: 400 : Bad Request, HTTP Error Code: 400 because the user already has the entitlement added.Is there any options to stop Add Entitlement operation from running in the Before Operation rule since it is already triggered inside Add Account api call?
You can achieve that by marking the flag createAccountWithEntReq to true. This flag ensures connector uses createAccount operation for adding the entitlements too as part of initial account creation.
Hi @uday_kilambi createAccountWithEntReq is alreadt set to true now which is causing an extra call of the Add Entitlement even though the entitlement is already set in the Create Account. So is there another setting I can do to prevent calling Add Entitlement for initial creation?
This should be the one to prevent it, can you share a screenshot of enabling this flag, add entitlement operation and also account schema for entitlement mapping
Managed to make some progress to remove the error by changing the the provisioning policy for Create Account to not use member_of and use createMemberOf instead.
However, request is still not completed. Did a search and seems like provisioning status needs to reach Finished? Any solution to fix the attributes getting stuck at committed?
The Get-Object operation would typically be the issue in this case. You need to ensure that the attributes returned from the operation are the same as the schema and what is being set in the provisioning policy.
If possible please could you share the response mapping from the Get-Object operation.
Hi @dylanfoggan I do not have a Get Object operation in my web service connector. I built it based on the api specs and it did not have this operation. Do I required a Get-Object operation? Do advise.
I would recommend you add that operation.
Essentially, it runs a single account aggregation after any changes have been done to the account through the connecter.
The API typically used in this operation is “Get Single User” since it is triggered after account changes.
Just ensure the response mapping is correctly defined to match the schema of the application and it should work as expected.
