Custom Function Database 13 - Parsing JSON

As with visiting any new country where they speak a different language, if you can’t speak it, then it’s pretty hard to communicate. The same thing applies to intercommunication between technical systems. If you don’t take the time to learn the format being used, then you obviously won’t get very far.

In this video, we take a look at processing JSON from GitHub’s API. It’s one of the last places we’re looking for FileMaker Custom functions. GitHub is a web site which hosts hundreds of thousands of code repositories. These code repositories represent many hundreds of thousands of coding hours. To not take advantage of any pre-existing resources seems a bit silly.

The trick to working with any cloud based resource is to simply learn what questions to ask and how to process the answers you get back. Of course, there’s always that critical piece of know-how which is all about processing the data in the first place. If you’ve never written a recursive FileMaker script, then you’ll certainly see some in action when dissecting the script in this version of our Custom Function database!

AttachmentSize
CustomFunctions13.zip691.13 KB

Comments

Hi Matt,
I sent you a email on this issue because, your site wouldn't accept my screen shots.
After I sent it, I have tried some additional things.
The Message script step is not grabbing the right message.
The screen shot I sent via email is only showing the name of the CF with Copy added to it. However, it did add the CF but didn't change the name of the <<prototype>>, but the content is the actual functions is there under the wrong name?

HTH, Lee