Let me copin in to @Phil first of all.
What we are doing now is just to simply apply action to import csv file, but against relatively high number of the set of rows and columns to import.
On our testing, the number of rows are 50k ish and column numbers are 25.
When we import such files, the action can be fired as we will see the normal dialogue box when the action start to import the file, but thereafter, App becomes completely sclient where we do believe that the backgroud operation is doing the job. The result is unstable, sometime the operation seems to be finished after 10 mins or so, otherwise we fail the whole stuffs. But App is not throwing any message if or not the operation is success or failed, as App is not throwing any error or success messages at the end when we upload relatiely large set of rows like this. We only know the fact the action failed through the app editor, monitors.
Then back to the question.
Can we get the technical limination where we will fail the import opreation due to the number of the rows/columns, more precisely number of the total cells in attempt to import? or In interms of the size of the csv file?
Let me assume we could gauge the limit which is exportable to Appsheet app in terms of the file size. Then could we get the error or rejection type of the message before the app ueser to proceed, such as โthe file size is too large. Reduce the number of the rows to importโ something like that.
Currently, the app stay quietn when we upload the large csv file. After 10 mins or so, we get to know if it is ended up with error or sucess through the app editor, which is just lke we are rolling a dice for a luck.
@Takuya_Miyai
LinkedIn
Twitter
