× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Just FYI this works.

**free
dcl-s json varchar(60)
inz('{"_id":1234, "stuff":"ABCD", "id":"XYZ"}');

dcl-ds data;
id char(3);
stuff char(4);
End-ds;

data-into data
%Data(json : 'case=any allowextra=yes')
%Parser('YAJL/YAJLINTO');

But of course, it assumes that there are no elements where handling of an underscore or other RPG-illegal characters occur in the json names.

Makes you wonder though who the idiot was who designed such a format!


Jon P.

On May 9, 2024, at 2:20 PM, Vinay Gavankar <vinaygav@xxxxxxxxx> wrote:

Hi,

I need to parse an incoming JSON string which has a field name "_id" and
another field name "id" among other fields.

I have defined only "id" in my data structure and am using
"allowextra=yes", hoping that it will ignore the field "_id". But my "id"
field gets populated with the value of "_id" field.

Is there any way I can get what I need without changing the incoming string?

TIA
Vinay
--
This is the RPG programming on IBM i (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@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.