Export CSV ON a Slice Still Exports Everything?

AppSheet AppSheet Q&A
,
1

Good Afternoon,

Im wondering Why CSV is still excporting my full table when I have the action set on a slice? Is this normal behaviour? How would one circumvent this without having a messy setup with copying rows to another table and have 100s of Syncs sitting there?

Thanks,

2

Yep that’s normal…doesn’t mean that’s the way it should be but it is how it works.

1 Like
3

I’m confused, Is this a bug? Or normal Behavior?
Is the Workaround I Mentioned the Correct way to go about this?

Thanks,

4

I used a view in a database and bring that in as my base table for CSV creation. I believe your workaround would work as well but would be a terrible pain. It is normal behavior as far as I have found. No one has responded saying its a bug.

5

All actions act on a table unless specifically configured in the action itself to use slices. Attaching an action to a slice in the slice configuration does not limit the action to affecting only the slice.

6

I believe I recall reading (but haven’t tried myself) that invoking an export-to-CSV action from a filtered view would limit the export to only that view’s data. You might try that.

A filtered view can be reached by clicking view in an inline deck, gallery, or table, or by navigating to a deep-link generated using LINKTOFILTEREDVIEW().

7

Perfect!, I’ll go with the filtered View approach.

Thanks,

1 Like