Sandbox User Modification Failures

Michael Conan

Is there a restriction on modifying users in the developer sandbox?

I appear to have at least one of the required roles to create/update/delete user phones, but I’m 0/3 in what I believe to be properly formatted requests.
Primarily attempting via Postman but also tried in the API explorer built into the docs.

Michael Conan

@Michael Conan
I'm now testing in a live environment, again both with Postman and the “Try It” functionality, again no success on any of the user phone endpoints.

Create:

Update:

Delete:

@Stephen Boyle can you provide any guidance / insight here?

Todd DeSchuiteneer

@Michael Conan, I am with Support and I have tested the POST, PATCH and DELETE routes against my own sandbox environment. In doing so I am able to successfully POST and DELETE but the PATCH route is giving me an unexpected 400 as you are reporting. I have reported this to our development team to address.

Regarding the POST and DELETE issues you are having I would like to look a bit more at this issue. I will reach out via support ticket to gather some additional information from you and begin troubleshooting.

Michael Conan

@Todd DeSchuiteneer circling back to this a bit later, I'm now seeing the errors again. Can you please confirm whether this was fixed or is failing still / again?

Todd DeSchuiteneer

@Michael Conan yes, that defect was solved on 4/30/24. Can you post the body of your Patch? I can run some tests and see if the issue has resurfaced.

Michael Conan

@Todd DeSchuiteneer
Yep, please see the example below. My objective is to update the type of the phone:

Users Phone Types - to retrieve source (Home) and target (Home 2) type IDs

User Phones by User - to retrieve phone ID for user to update

Users Phone Update - to update type of user phone, unsuccessful

It did allow me to update the number itself, but my requirement is to update the type, not the number.

The documentation for the endpoint seems to suggest that I should be able to update either / both values.

Todd DeSchuiteneer

@Michael Conan the way the phone update works you cannot update the type on phone number. If you need to create a new type for a phone number the best course of action would be to delete the phone record and create a new record with the new type.

Michael Conan

@Todd DeSchuiteneer

Okay that’s the workaround I’m using now, it’s quite painful unfortunately as I also need to recreate all of the links, so it ends up being a number of calls rather than a single update…

Todd DeSchuiteneer

@Michael Conan understood. I'll bring up this pain point with the team and see if there are any improvements we can make in the future to be able to update the types instead of completely removing the record and recreating it.

Michael Conan

@Todd DeSchuiteneer
Much appreciated - I believe this may be a broader limitation as I've observed similar challenges in updating record “type” fields with the OneRoster API, which also make the integrations and platform more difficult to use