This is interesting.
Inspired by your post, I did some quick test to see how Appsheet is going to behaive.
My perception.
We create action to export data to CSV. Then attach this Action either 1) Table or 2) slice.
The view being generated out of Table or Slice with this actoin will download ENTIRE data from either slice or table down to CSV.
But my test showed it was not true.
Let me explain what I newly found.
Do the usual job to create action to export to CSV. We can attach whatever table or slice we want.
Then create view out of them. For instance, table, deck , gallery, whatsoever.
On your use case, we create the mechanism like this. From User table, such as table view with listed users, then by action (fired upon select) bringing to FILTEREDVIEW with that expression, we will be prompted to the table or slice where we will see the conditional view where we will find the selected row based on filteredview expression. Lets say, once selecting the one of the named user out of user list view, then we will see filtered view where we will see the rows associated with this selected users. We already attached action (export to csv) to this base view for this filtered view, so we will see the acitn button to export to CSV.
Hit this acion icon.
yes, we will download only the rows which was returned by the filteredview, not entire row out of table / slice.
LESSON LEARNED ;
In the action setting, Export CSV is said to be
“Export THIS VIEW to the CSV file”
The important point is “THIS VIEW” in this context.
Fireing export to csv action, Appsheet will look into the current view, regardless of whole table/slice or filtered view.
At the end, we wil export data only contains filtered view at the end.
Appsheet is amazing!!!
LinkedIn
Twitter
