JSON Limitations

Options

I have an external API that returns a JSON ~6000 lines of data (approx 1MB), that nests objects about ~10 levels deep at points.

I'm finding that when the result is displayed in the debugger, some of the arrays are displaying as empty.

To give you an idea of specifics, for the key-value pair headings is found at

response.result.data.insights.lh.audits.example.headings

The value of headings appears as follows:

"details": {
"type": "table",

"headings": [
{
"key": "node",
"valueType": "node",
"subItemsHeading": {
"key": "relatedNode",
"valueType": "node"
},
"label": "Failing Elements"
}
],

Not sure if this is a problem with the JSON syntax, xano debugger, xano memory, or something else entirely.

Is it fixable?

Thanks in advance!

Tagged:

Answers

  • mzcodes
    mzcodes Member
    edited March 2023
    Options

    Sorry, not sure why my json was cut, trying again, using a screenshot since my codeblock doesn't want to display:

    Thanks again

  • Chris Coleman
    Chris Coleman Administrator

    ADMIN

    Options

    Hey there! Can you post a screenshot of what this section looks like from the debugger in Xano?

  • mzcodes
    mzcodes Member
    Options

    Thanks for the quick response! I think the issue may have to do with how xano is assembling the query string versus how it occurs in postman, resulting in different outcomes from the api.

    I'm going to keep testing this hypothesis and will confirm what I find.

  • mzcodes
    mzcodes Member
    edited March 2023
    Options

    I looked into this a bit more, and I believe the issue may be with how I've implemented the API call in Xano.

    Thanks for your help!