We have an external system that makes REST API calls to the SalesOrder endpoint. Every once in a while the resulting JSon has null for all Usr fields. I can refresh the data and the result will have all field values.
The other day we added code in the graph extension’s initialization routine to access some custom fields in a setup table. Then we started to see the occasional error because those calls to GetExtension were failing. But only once in a while. But when they started to fail, they continued to fail, over and over, for a period of time. Sometimes we restarted Acumatica, sometimes the error just went away.
I removed the code from the initialization routine and things were better.
Doing some stress testing today, forcing ACM to send me the GET result from the order over and over, we’d get to a point where the JSon result was showing null values in all custom fields. The base fields still contained data. No change to the underlying transactional data - just sending multiple GET requests with the same http connection.
It’s like the graph extensions didn’t get loaded and thus the various views didn’t know what the custom fields were and so the result was null.
Has anyone seen this happen with the REST API?
Best answer by Dmitrii Naumov
View original
