Hey @James_Naylor !
I used to solve this in two ways:
-
through a form that captures and submits the data to a private doc. Then I can code whatever processing I need in that other doc, including composing the CSV and emailing it to the client:
🍕 Viva Pizza: Making a secure storefront (pizza delivery) on Coda
-
through a custom pack formula, but I had to deliberately make the formula not an action, and make sure it’s only invoked once at a button click. Action formulas are deactivated in play mode but non-action formulas aren’t. It’s a very bad design to make non-action formulas that have side effects (i.e. change something and thus cannot be called repeatedly at any time) but it’s a justified workaround.
Coaching · Work with Coda Tricks
— Leave Your Email functionality is built this way
Generally yes, the challenge is to somehow capture the data the user has in their sandbox (because play mode is a sandbox, the changes aren’t saved to Coda anywhere and only exist in that tab) and pass it somehow where it can be stored and processed.