Assure DQ

Hi Support,

Trying to read JSON formatted file. But everytime I try to pull up memberid field so I can count how many member ids in a file, I keep only getting the first one. the rest of the memberid in the file for some reason aren't showing when I do a test layout. Attached is an image of the file. We played around the root, and the many/once settings. We are getting the same results. Is there a way json needs to be formatted to be able to read multiple records? or any suggestions we can make in our layout to be able to pull up ALL memberids correctly.

Hi JL.... The current version of the JSON plugin is very strict in regards to consistencies in the fields. The fields defined in the layout need to match the same order as the fields in the input source. In addition, the "Generate Fields" button in a Layout will only check the first record for the fields to add. If subsequent records in the input source have different or additional fields, those fields will also need to be manually added to the Layout.

There are plan to enhance the JSON plugin to be more forgiving to field order, however, there is no set time frame as of right now on when that will be available.

Thanks Jeff. I remember now, that I have created a case on this before and it seems to be the same issue that Gerard helped us with. That we have to define ALL fields in the json file for it to read the next set of data.

If i want to read specific root/field in the json file to make the reading of the file faster, can i just use the field as the root?  it seems that i can but if i test the layout it remains to pick up only just one. and if i change the instance to many, I end up not getting anything. I attached the file. I'm trying to read memberId only. 

attaching the file used. not sure if it went thru in my previous post

Attached files

Attached files

Testing3_Array.json

Hi JL,

  For optimal speed, the root level should be defined as the lowest level field that contains the array of fields to extract. This would be one (or more) level up from the data itself, rather than defining the root at the field level.

Jeff