Power Query issue with Appian

What do you mean by “power query”?

Are you using an Appian API to get the data from Appian? If yes then, can you check your json response from API if it has all the columns intended.   

You do not describe what you are actually doing. Please explain in more detail.

Please describe in detail.
Also, you can export at most 50 columns. And make sure you should only export data from your site and not export grid data from an interface in Appian Designer.

Thanks everyone. To clarify, I am not exporting grid data from an interface/Appian Designer.

I have an Appian Web API that queries a report DSE/entity using a!queryEntity(), casts the data to a helper CDT, and returns the result as JSON using a!toJson(). This Web API is then consumed in Excel Power Query.

The helper CDT has 50 fields. All fields are coming correctly except one field: desiredAllocAtCommitment, which is a Number Decimal field.

The strange behavior is:

• When the API returns the full dataset, around 10,000+ rows, this field does not appear in Power Query.
• When I reduce the total record count using pagination/limited batch size, the same field starts appearing.
• The field exists in the source table and helper CDT.
• Other columns before and after this field are appearing correctly.

I am checking the raw JSON response directly from the Web API to confirm whether desiredAllocAtCommitment is present there. If it is present in JSON, then it may be a Power Query expand/sampling issue. If it is missing in JSON, then it may be related to Appian serialization or response size.

Has anyone handled a similar Web API + Power Query scenario? Would the recommended approach be to expose pagination parameters and let Power Query pull the data in smaller batches?

Can you just expose a batchNumber / pageNumber in your API and return the data in batches of 1000 rows and have Power Query loop through that?