Size issue/limit with the PowerApps JSON function

[paulsnolan]

Hi All

Is there a size issue/limit with the PowerApps JSON function. I have a collection that I format using the JSON function and then send to Flow to export as a csv file. This works fine up to a limit. Once I get to around 3500 rows the JSON function fails silently and the Flow, which is the next command in my OnSelect function statement, doesn’t run. The button used to trigger the JSON function and Flow remains in a disabled state. Does the PowerApps JSON function have a byte/char limit for the size of data it can process?

Regards

[gabibalaban]

Hi @paulsnolan ,

Have you tried also using  - JSON (yourcollection, JSONFormat.Compact)

Hope it helps !

[timl]

Hi @paulsnolan 

Yes, there is a size limit that is associated with the JSON function.

Although there is nothing in the documentation that specifies what this is, other users have encountered this problem and it typically happens at around the 3,000 -5,000 row mark.

[paulsnolan]

Hi @timl

This looks like a data size issue. The variation in row count, which appears to give rise to the issue, I would guess is related to the size of the rows in the user's collections.

[paulsnolan]

Hi @gabibalaban 

This made no difference

[timl]

Hi @paulsnolan 

Yes, I agree. This is an issue that is definitely related to data size.

I'm not sure what the exact size limit is and as far as I'm aware, we have not had any official clarification as to what this is.

[paulsnolan]

Do Microsoft contribute to these community discussions, would be good to have their input regarding this issue?

[markfleet]

This is still an issue which I do not feel relates to available memory.

This can be demonstrated by running the below. Variable "jsontest" will be empty. If the Sequence function is changed to 4000 then the variable will be set correctly.

Set(jsontest, Blank());

Clear(colDummyColForJson);

ForAll(Sequence(5000),

Collect(colDummyColForJson, {RowIndex: CountRows(colDummyColForJson) + 1})

);

Set(jsontest, JSON(colDummyColForJson))

[cbjmp]

I found that it's the size of the collection, not the number of records.  I made a second collection from the one I wanted to export, excluding large data fields, and it worked better.  I read the limit is 0.5Mb - which seems about right.