New post
Question
· Aug 30, 2017

Retrieving values from JSON %Library.DynamicObject (2017.1)

#Beginner #JSON #ObjectScript #Caché

Good afternoon - 

I'm in the process of learning to make COS calls to REST-based web services and while I am having success, I'm struggling on how to parse out the results (I admit I'm very green at this):

Here's the code retrieving the JSON response:

w !,"Get the JSON"
Set Result = {}.%FromJSON(Request.HttpResponse.Data)

This has Result as a Library.DynamicObject.

I can then write out the response using:

w !,Result.%ToJSON()

This works, I can see the response is valid and what I want. Here is the JSON returned (de-identified):
 

{
  "RecordIDs": [
    {
      "ID": "1234",
      "Type": "INTERNAL"
    },
    {
      "ID": "1234",
      "Type": "EXTERNAL"
    }
  ],
  "ContactIDs": null,
  "Items": [
    {
      "ItemNumber": "320",
      "Value": null,
      "Lines": [
        {
          "LineNumber": 0,
          "Value": "1",
          "Sublines": null
        },
        {
          "LineNumber": 1,
          "Value": "100063287",
          "Sublines": null
        }
      ]
    }
  ]
}

What is the easiest method to get the LineNumber Values out? I could potentially have several so I'm trying to get an output kind of like Value1~Value2~Value3 so I can piece them out later.

Appreciate any advice - I'll keep pluggin away on it. 

Discussion (4)1
Log in or sign up to continue
Eduard Lebedyuk · Aug 30, 2017 
set obj = {"RecordIDs":[{"ID":"1234","Type":"INTERNAL"},{"ID":"1234","Type":"EXTERNAL"}],"ContactIDs":null,"Items":[{"ItemNumber":"320","Value":null,"Lines":[{"LineNumber":0,"Value":"1","Sublines":null},{"LineNumber":1,"Value":"100063287","Sublines":null}]}]}
w obj.Items.%Get(0).Lines.%Get(0).LineNumber
>0
w obj.Items.%Get(0).Lines.%Get(1).LineNumber
>1

To iterate over arbitrary number of array elements use iterator:

set iterator =  obj.Items.%Get(0).Lines.%GetIterator()
while iterator.%GetNext(.key,.line) { w line.LineNumber,! }
>0
>1
3 0
Craig Regester Aug 30, 2017 to Robert Cemper

Thanks for your answer as well! This is actually what we were already doing with 2015.1 when handling JSON. So moving into 2017.1, I was hoping to make more use of the built-in JSON handlers because the JSON response I posted was a rather simple one - some of our more complex responses has our string manipulations getting quite long-in-the-tooth. 

0 0