We are building a simple REST interface with a REST connector.
While saving this question pops up.
Which answer will prevent unexpected behaviour when modelling a POST and a GET?
It was a while since I sat with the REST Connector in Classic, it works differently in Connect. I know I have seen that, it is what it says more or less. You set an entity header on a parent in the model, and it asks if you want to propagate it to its children.
I remember way back in the pandemic era, I set a rest connector up for Zendesk and recorded the process, perhaps it helps somewhat: https://www.youtube.com/watch?v=dGnmrHeiydg
It depends on what header you have set on the higher level and the effects of that header on child operations.
Have you configured a header on the top level?
On top level seems to be one header which doesn’t contain any value.
We did not configure this ourselves. Is it a default?
In case the connector has a lot of similar headers then choose Yes.
In case the connector has a lot of different headers then choose No.
Can you say this generally?
Have never seen that as a default setup no. I would remove it and set headers on operation level.
If the operations in a container (folder) all use that same header it makes sense to put it in the root and use inheritance in the operations.
As an example of content type; if you send JSON payload in all your operation in a container, set it to “application/json” and use inheritance. If you mix operations in a container, GET,PUT,POST or even different services, I would instead set the headers on operation level since the different requests will (probably) require different headers.
