Hello everyone,
I wanted to share a small but important detail about REST API behavior differences between Classic UI and Modern UI.
I think the general expectation is that UI changes do not/should not affect API behavior. But it’s not completely true.
The REST API behavior does depend on the UI of the mapped screen. The order of containers in which REST API processes the request is bound to the order these containers are defined in aspx.
E.g. if you have the following mapping structure the order of writing Details and TaxDetails depends on which of these containers is defined first in the aspx of the screen.
{
"DocType": {"value":"Invoice"},
"RefNbr": {"value":"012345"}
"Details": [...]
"TaxDetails": [...]
}When a user switches UI to the modern one, we do not have aspx anymore. But now, the order will be taken from the typescript definition of the screen. The same rule applies - the first container defined in the typescript will be processed first by the API.
That may cause an issue. If the order of containers defined in aspx differs from the order of views defined in typescript, switching UI actually does change the REST API behavior as well.
Please be aware of that. If you see the behavior changing in one of the default APIs with switching UIs, please report it in a support case.
