Re: DATA-INTO - Different JSON depending on succeed or fail

Yep... that's how most people return JSON data when there is an error...

Could you build the error structure into your DS along with the successful
layout, put the data into it then check if there is an error that way? I
guess I've never tried that. I always use the YAJL APIs so I can first
check for an error code.

On Mon, Dec 19, 2022 at 9:47 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

Unless the HTTP response code differentiates between the two types of
response the only other way I can think of doing it would be to use the raw
YAJL APIs and interrogate the JSON that way - either looking for a specific
element or from the looks of your data you could just check if you have an
array or not.


Jon P

On Dec 18, 2022, at 11:43 PM, Don Brown via MIDRANGE-L <

midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Hi

We are dealing with a new provider and are consuming their service.

They reply with two completely different JSON formats depending if the
request is successful or not. And neither are named.

For example

if error found on the request , then the return data provides the

response

details

{
"responseType": "executeQuery",
"responseTime": 1669597839789,
"responseCode": 104,
"errorCode": 0,
"message": "Parameter Error: Custom Report Exception: Parameter
2022-11-10 :00:00 and 2022-11-10 23:59:59 must be timestamps in the

format

YYYY-DD-MM HH:MM:SS"
}

Whereas if the request is successful we get an array of data

[
{ "RequestedDate":"2022-11-10", ....... },
{ "RequestedDate":"2022-11-11", ....... },
{ ... }
]


So what we are doing is attempting a DATA-INTO into the successful data
structure and if that fails attempting to load into the response data
structure.

While this works I was just wondering if there is a better option to be
able to determine which response received and therefore retrieve into

the

respective data structure rather than the trial and error approach


Thanks for any suggestions

Don



--
This email has been scanned for computer viruses. Although MSD has taken

reasonable precautions to ensure no viruses are present in this email, MSD
cannot accept responsibility for any loss or damage arising from the use of
this email or attachments..

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

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