Re: Handling JSON object/array nulls in DATA-INTO

Your DS does not match the document. Here's a version that works.

dcl-s json varchar(1000)
inz('{"path": "/test/34234234.pdf", "timeout": 0, "parms": null}');

dcl-ds pathDS qualified;
path varchar(200);
timeout int(10);
parms varchar(100);
end-ds;

Given that you show parms as a DS (and going on the ds name) I'm thinking it should be perhaps an array rather than a DS? How about showing us an example of the json that includes all values?

Also I don't know where you got "size" from - it doesn't exist in the json. Avoid using allowmissing if possible. If size is indeed missing from the doc then use countprefix as per previous examples here.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jan 11, 2019, at 11:09 AM, Ryan Cronin <rcronin@xxxxxxxxxxxxxxxxx> wrote:

Hello,

I have the following JSON example that is causing some issues with the DATA-INTO feature.

JSON:
dcl-s json varchar(1000) inz('{"path": "/test/34234234.pdf", "timeout": 0, "parms": null}');

RPG:
dcl-ds pathDS qualified;
path varchar(200);
timeout int(10);
dcl-ds parms;
type varchar(100);
size int(10);
end-ds
end-ds;

data-into pathDS %data(json:'case=any allowmissing=yes') %parser('YAJLINTO');


Does anyone have any advice on how to get this to work properly?

Thanks,

Ryan Cronin
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com