What I chose to do is add a JSONExtractor. Then under the Extract Queries configuration box I created each of the attributes that I wanted to see in the Target Attribute column. Then in the JSON Query the JSON Query is simply json["Key"].

Hello @abysmal-ukulele​ 

The JSONFragmenter & JSONExtractor combination is definitely one option.

FYI the JSONFragmenter also has options to flatten query results into attributes within the transformer itself. Once this parameter enabled, the transformer will automatically flatten any key value pairs into attribute names and values. Note that you do have to manually enter the key names to expose them either within the Attributes to Expose parameter of the JSONFragmenter or use an AttributeExposer.

Hi @debbiatsafe​ Thanks for that. I swear I had tried to do the very thing that you're picturing but it didn't work. I couldn't figure out where I had gone wrong. I tried different syntax with no success. Of course, once I read your post the transformer behaved.

If anyone else is struggling with the JSONFragmenter it is worth mentioning that each entry within the 'Attributes to Expose' fields do not require quotations. The entries need to reflect the Key Value exactly.  

Thanks for steering me in the right direction.

So here is an instance of the JSONFragmenter not working as expected.

First see how I configured the transformer in picture 1.  

You can see the JSON from the _http_response_body in picture 2. 

In picture 3 you can see the very last column "comments" has not been populated.

What did I do wrong? @debbiatsafe​ Maybe you'll have some insight?

Okay @debbiatsafe​ last message about this I swear...

So I understand where I went wrong. If I had to categorize it I would say that I didn't quite understand when or what exactly the JSONFragmenter was flattening. I thought the JSONFragmenter was flattening the input JSON text. In my post above, I have shown the text arriving into the jsonFragmenter (pic 2).

The JSONFragmenter is flattenting the content after it has been processed and is found in the _response_body attribute. The JSON Query that I created in my previous post: json["Comments"][*]["Comments"] removed the key value pair and left only the content associated with a comment. Without the key value the flattener did not work. So when creating a JSON query to be flattened less is more, in a sense. The json query one creates should maintain the key value pairs. So the json query: json["Comments"][*] , is a query that works since it maintains key value pairs.

Hopefully this explanation will help someone else. Understanding what is being flattened and at what stage of processing is helpful when using the transformer.