V12 Web Service Messaging

SUGGESTED

This is sort of different than another thread on null web service messaging, maybe they're related, I'm not sure. My issue is that in V9, when submitting a sales order via web services, if there was an error, the resultxml messages array would have helpful messages as to why the order didn't succeed.

This is 9.0.3.

In 12.0.21, that helpful message is gone, and all I get (essentially) is that it can't handle popups in web services. (Sorry about the picture, the text doesn't wrap.)

Has anyone encountered this, and if so can it be returned to the way it was? Do I need to do something differently to get those better messages back?

Thanks.

  • 0

    Jim, did you try manually entering the same order in X3, so you can see what the pop-up message is?  Is it still because of the inactive customer?  Sage is supposed to have all pop-ups disabled for the sales order when calling from a web service.  The only time I have had issues with pop-ups in V12 is when it's related to an Avalara message.  The Avalara messages don't seem to be disabled for web service calls for sales order entry.  We had one client where we actually had to modify the standard code to suppress the Avalara messages during a web service call for order entry.  

  • 0 in reply to Denise Hartman

    I get the same 'field error: sold-to - inactive customer' popup if I try to enter an order for the same customer in both versions. (That's true, the customer is inactive.) 

    I wondered what the errors look like on submitting an order with restricted products, something we use extensively. In that case, the array has four messages.

    (2-warning) "Do you want to re-calculate the requested delivery date from the current date?   (No)"
    (2-warning) "Delivery lead-time is modified : Recalculation of the shipment date"
    (3-error) "Prohibited Product"
    (3-error) "Field error [M:SOH4]ITMREF"

    So, this is at least similar to V9 and still usable.

  • 0
    SUGGESTED

    This is a known issue with V11 and V12.    There was a partial fix in the later versions of Syracuse, which you would also still need to apply, but the fix for the error reporting didn't get shipped until 11.0.17 and 12.0.23 patch sets

    Hope this helps