I know Support is going to come back and blame my customizations, but why would it start occurring months after the customization on Order Entry was released?
Not sure why the call would fail, and even more so, why the functionality still works, but throws the error anyway. The users are getting this on Customer Credit Manager, Order Entry, Customer Shipment Entry… I’m confused.
in application studio is there a rest call that is referencing a field that can be null? Seems that error happens when the object is empty so maybe throw a zero on whatever field your rest-kinetic call I assume is referencing?
I say open browser dev tools, watch the network tab and watch the call. You can see everything that’s trying to be sent and any responses - OR worst case, you dont see it and it’s failing before the call (putting the blame squarely on the client side)
So fun thing - I didn’t have as much time as I thought to test this out, and we had flexed our upgrade to this past weekend.
I just checked in with the userbase now that we are upgraded to the “latest and greatest”, and the rest error is no longer coming up. Version issues causing it??
