@Austin-Gilliam
It looks to me like your JSON is a JSON string representation of a JSON array. This means that the parse() RemesPath function (follow that link, then find the parse() function) will help you. It attempts to parse a JSON string, and returns an object that either has result: (the result of parsing) or error: (the error that caused parsing to fail). Note that this function was added in a pretty recent version (v5.5.0), so you might want to get the latest version if that query fails.
Here’s an image of what we get with your JSON.
[image: 1702689231522-1191f8b3-c9b2-4d98-b544-5511e06b6143-image.png]
As you can see from the treeview on the right, the parse() function worked. Since we know it’s successful, I’ll just change the query slightly, to parse(@).result (which extracts the result value). Now I just click the Save query result button above the tree, and the parsed array is saved in a new buffer. The contents of this buffer will be as follows:
{
"FastenerData": {
"508670": {"Item1": "10", "Item2": "50"},
"508674": {"Item1": "10", "Item2": "50"}
}
}
By the way, I’m the maintainer of JsonTools, and you can always raise an issue in the repo (linked here) if you need help. But this is a fine place to do it as well.
@PeterJones
I’m pleased to see that you noticed the potential of Dump JSON string(s) as raw text in this situation. I was just about to mention it, but I saw you beat me to the punch.