JSONQuery at FM-DiSC

15 thoughts on “JSONQuery at FM-DiSC”

1. Just watched the presentation – Brilliant!

   Reply

   1. Thank you, Paul!

      Reply

2. Great presentation! Thank you for all your work on this. (Look forward to trying the path function!)

   Reply

   1. Thanks, Ben! I will be working on the remaining QA for the upcoming version this weekend. I think that after that plus one more weekend of similar work, it will be ready for release. Glad you are interested in the PATH function. It was your comment on the first post in the series that inspired it!

      Reply

3. I used JSONQuery in my 10 FEB 2022 presentation for DIGfm! Thanks to STEVE_SSH for the assist:
   https://community.claris.com/en/s/question/0D53w00005cl7IlCAI/digfm-packing-my-json-ready-to-travel-on-the-path-2102022

   Reply

4. Is there a repository for getting the latest version of JSONQuery or do individuals need to come to this site to download the file?

   Reply

   1. Hi Jay,

      Currently we are the repository and the current version is on this page.

      Regards,
      Kevin

      Reply

5. Just starting to play with this CF but am having difficulties. I have validated that the json I’m using is good but any/every JSONQuery I use only returns a pair of brackets – thoughts?

   Reply

   1. Hello Karstyn. Thank you for trying out JSONQuery, and for reaching out about this. I would be happy to try to help you out with some ideas, tips, or even potentially spot an error if you can provide some detail. At the very least, seeing the parameters that you are supplying to the function, and a statement about what you were expecting to be returned would be an excellent first step towards being able to offer some helpful feedback. Including a small sample of your JSON would also be helpful, if that is possible. Thank you, Karstyn.

      Reply

6. Karstyn,

   An empty array as the response indicates that there were no matches for your query.

   Can you please post a) sample source JSON and b) JSONQuery syntax that is returning “[]”?

   Regards,
   Kevin

   Reply

   1. Thanks for the quick response!

      Here is some cutdown and anonymized json:

      {
   "paging" :
   {
      "next" :
      {
         "after" : "ODg3ZDMwN2MtODQzYi00Mj",
         "link" : "?after=Q&limit=20"
      }
   },
   "results" :
   [
      {
         "url" : "https://xyz.com",
         "submittedAt" : 1717177149663,
         "values" :
         [
            {
               "name" : "time_zone",
               "objectTypeId" : "0-1",
               "value" : "EST"
            },
            {
               "name" : "intro_to_fm",
               "objectTypeId" : "0-1",
               "value" : "June 4, 2024"
            }
         ]
      },
      {
         "url" : "https://xyz.com/register/",
         "submittedAt" : 1712084618623,
         "values" :
         [
            {
               "name" : "time_zone",
               "objectTypeId" : "0-1",
               "value" : "EST"
            },
            {
               "name" : "intermediate_fm",
               "objectTypeId" : "0-1",
               "value" : "June 5-6, 2024"
            }
         ]
      }
   ]
}

      and the JSONQuery I tried:

      JSONQuery ( JSON ; "results" ; "MATCH_ALL" ; "" ; "" ; "LIST (results.submittedAt )" )

      Reply

7. I would recommend simplifying things by first extracting the results array, and then running your query against that simplified input. E.g.,

   Let ( x = JSONGetElement ( JSON ; "results" ) ;
      JSONQuery ( x ; "" ; "MATCH_ALL" ;
      "" ; "" ; "List ( submittedAt )" )
)

   Hope this helps,
   Kevin

   Reply

8. I agree with Kevin. The first argument supplied to JSONQuery should be the array that you are querying. The example that Kevin posted looks good to me. I’d suggest giving it a try. Thank you Karstyn for providing details, and thank you Kevin for providing a great answer.

   Reply

   1. And thank you most of all to you Steve, for making it all possible.

      Reply

      1. That worked perfectly! Lesson learned.

         Thank you both!!

         Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.