I am sure I have seen someone else with this error but searching the archives has not found the incident.
The JSON has a double [[ ]] indicating two arrays. If I remove one set (leaving [ ] ) it processes correctly with the data structure below.
So, we have an unnamed array inside an array, how do we build the data structure for that ?
We have this JSON
{"error_details":[
["34515897: meter_off_time 2025-10-06 01:57:06+00:00 is equal to or before meter_on_time '2025-10-06 02:45:04+00:00'"] ], "errored_booking_numbers":["34515897"],
indicates that the document is not an external file. The parser is
'YAJLINTO'. *N indicates that the parser is a procedure pointer.
Recovery . . . : Contact the person responsible for program maintenance to
determine the cause of the problem.
Technical description . . . . . . . . : Reason codes and their meanings are
as follows:
1. The specified path to the name was not found in the document.
2. The document contains too few array elements for array subfields of a
data structure.
3. The document contains too many array elements for array subfields of a
data structure.
4. The document is missing information to match subfields.
5. The document contains extra names that do not match subfields.
6. The document contains text content within the content for the subfields
of a data structure.
7. The document contains subfield items for RPG scalar fields, subfields or
Any assistance appreciated.
Thanks
Don
Brisbane - Sydney - Melbourne
Don Brown
Senior Consultant
P: 1300 088 400
DISCLAIMER. Before opening any attachments, check them for viruses and defects. This email and its attachments may contain confidential information. If you are not the intended recipient, please do not read, distribute or copy this email or its attachments but notify sender and delete it. Any views expressed in this email are those of the individual sender
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.