Hello Experts I am unable to call the beta version update account API using JSON Patch standards. Facing the error – not a valid patch field for the account model update-account | SailPoint Developer Community Update Account Requirement: Update account AP…

I did some testing on my personal tenant, and here is what I found. You can do a PUT request to update account attributes. A PUT request will trigger account aggregation automatically, which you can track with the task ID that is returned from the PUT request. A word of caution, you must provide …

Can you share with us the JSON payload you sent in the request as well as the exact response?

Update account works fine for delimited sources, but not the G suite (which is a connected source) with below payload. I expected that this would initiate attribute level provisioning on source account. JSON paylaod: { “attributes”:{ “ primaryEmail":"xyz@abc.com ” } }

That payload isn’t valid for PATCH. PATCH requires the following structure: [ { "op": "replace", "path": "/identityId", "value": "2c9180845d1edece015d27a975983e21" } ] Your payload looks like it is formatted for the PUT endpoint: put-account | SailPoint Developer…

Hey @colin_mckibben … thanks very much for the response. :slight_smile: Tried this as well and the error I have got is something similar to “Syntactically correct but semantically incorrect” Also, quick thing – Is the beta API for update account expected to provision attributes or is it just for …

@colin_mckibben Nice to really fast responses. thank you very much for this. I will try this out and keep you posted. – Thanks Sandilya Krovvidi

@colin_mckibben Thanks for providing this. However, as discussed previously, this call is working for delimited files only and not for the connected sources… Is this a bug or an expected behaviour? If it’s a behaviour, I will raise an idea for this… Please let me know accordingly.

Sounds like a bug. Can you manually trigger account aggregation on your connected source after running the PUT command? PUT should trigger aggregations regardless of delimited or connected source. Can you submit a support ticket at https://support.sailpoint.com ?

[image] colin_mckibben: T should trigger aggregations regardless of delimited or connected source. Can you submit a support ticket at https://support.sailpoint.com ? My customer would not be using this feature because of issues we found. Can I still raise a bug as a partner?

Hi @SandilyaKrovvidi We might want to back up a little bit. Can you tell me what you are trying to do? The v3 / beta accounts end-point is for modifying already aggregated accounts. This end-point only lets you update the identity reference, which will move / re-correlate the account to a new id…

I just stumbled on this article doing a search and apparently the functionality is better documented in the V3 version of the API (BETA should probably be updated also or a reference provided to V3) https://developer.sailpoint.com/idn/api/v3/update-account Update Account Use this API to modify the…

IdentityNow - Update Account API

Identity Security Cloud (ISC) ISC Discussion and Questions

SandilyaKrovvidi (Sandilya Krovvidi) April 7, 2021, 10:54am 10

My customer would not be using this feature because of issues we found. Can I still raise a bug as a partner?

Topic		Replies	Views
Account update (patch) not working and throwing is not a valid patch field for the account model ISC Discussion and Questions apis , identity-security-cloud	3	395	August 22, 2023
Account patch api clarification ISC Discussion and Questions	4	453	July 19, 2023
POST /api/account/setAccountData Non-Public API Deprecations deprecated	4	896	July 10, 2023
Updating attributes using /v3/accounts ISC Discussion and Questions apis , identity-security-cloud	2	623	July 19, 2023
Account API inconsistency json format General Feedback apis , identity-security-cloud , accounts	0	435	August 29, 2023

IdentityNow - Update Account API

Related topics