At first, I thought this was a more serious issue than it turned out to be, but still something that needs to be fixed.

We were having issues with our JSON API class this morning, which turned out to be because FedEx has decided to start returning slightly different JSON for a single package shipment than they do for a multiple package shipment. But while working through the issue I ran into an issue with JSON rendering in the debugger.

The JSON being returned from Fedex is fairly complex with several nested arrays etc. I create a simple program to submit the issue to support, with the following code in it

Content is string = fLoadText(CompleteDir(fDataDir()) + "content.txt")



Json1 is JSON = Content

Trace(Json1.transactionId)

Trace(Json1.output.transactionShipments[1].pieceResponses[1].trackingNumber)

And I set a debug at the end of that code. When we view Json1 in the debugger it looks like output is empty

However, if we look at Json1.output.transactionShipments[1].pieceResponses[1].trackingNumber we can clearly see it has a value.

And if we look at content we can see that output has all kinds of data in it

Running this same test code in v28, the debugger correctly shows output

So the good news is that this isn’t a show stopper we are still able to address all the JSON data, it just makes it inconvenient when trying to debug or test out code. Especially considering when I work on a accessing a new RESTful web service, the first thing I do is look at the returned JSON in the debugger to help me figure out how to proceed with accessing the data.

• WX