Help with using the POST Request API

Matt Storm

Hi,

Hope someone here can help. I'd like to use the SKY API Add-ins connector in Power Platform to use the POST Request API.

If I want to change a request, the documentation says the json body of the API should have the following format:

This is the basic structure of the requests table when I use the GET Requests API:

I'm using a SKY API Add-ins "send an HTTP request" action. I can change the fields in the custom_fields section using code such as below.

What I'm not sure of is how to update the other sections of the requests table. By section I mean.

• project_title would be an example of layer 1.
• organization_id/name, would be an example of layer 2.
• Codings would be an example of layer 3

For example, if I tried to update the project_title using the code below, it will tell me that the custom field project_title doesn't exist.

Does anyone know the correct format for using this API for the different sections?

Thanks in advance

Erik Leaver

Hi Matt, I tested this in the try-it console and a colleague tested in postman. We observed the same behavior - only the custom fields are able to be updated.

Please file a support case & reference it here so I can follow. The request to support should be to validate that only the custom fields can be updated and request if this was the intended behavior from products. I can help with any needed documentation updates. And if these fields can't be updated, I can help raise visibility if you create an idea for the ideas bank to add this functionality.

Valerie Marshall

I am very interested in the outcome of this!

Erik Leaver

@Matt Storm were you able to create a support case?

Matt Storm

Hi,

It took a few weeks to raise a support ticket, as I wasn’t familiar with the process—the chat feature wasn’t working for me, I couldn’t reach anyone by phone, and it took some time to locate the correct email address. It turns out that everything in the UK is handled by Buzzacott.

After discussing it with Buzzacott, I get the impression the current functionality is intentional. Many fields in the requests table are tied to ID fields, so it would make sense not to allow the description of the ID field to be updatable, as otherwise it could cause issues in the back end. So, limiting the API to only update custom fields would keep things simpler and avoid complications.

That said, I’ve asked Buzzacott if they can raise it with BB as I'd like to hear the official answer. I've not heard anything back yet. I'll update this feed when I do hear something.

The Buzzacott support ticket number is: C-27611 if that helps.

Matt Storm

I heard back from BB—they’ve asked me to add this to the BB Idea Bank. If you think this feature would be helpful, please up vote using the link below.

https://bbgm.ideas.aha.io/ideas/GMK-I-1917