Can’t export JS / Joined List values except by manual Data → Export

Ask for Help
1

Hi everyone,

I’m stuck with what feels like a hard limitation and want to confirm if there is any supported workaround.

Setup

  • I have a 1‑row helper table called Operaciones query.

  • In that table I do all the logic using:

    • Conditional Relations

    • Joined List columns

    • A JavaScript (Experimental Code) column

  • The outputs I need (lists of cleaners, counts, etc.) only exist thanks to those computed columns.

What does work

If I open the Data Editor, go to Operaciones query and click Export, the CSV I download includes the correct values from those computed columns. So Glide can compute and export them in that context.

What I’ve tried that fails

  1. Scheduled workflow + Set Column Values

    • Trigger: Every X minutes/hours.

    • Steps: Query Operaciones query → Loop → Set Column Values (copy from JS / Joined List into basic columns).

    • Result: I get the red warning:
      “This scheduled workflow uses unsupported Experimental Code columns.”

    • The Set Column Values step writes nothing; the basic columns stay empty.

  2. Scheduled workflow + Create CSV file / Create JSON

    • Same table, same row.

    • The generated CSV/JSON has all the columns present but the values from the JS / Joined List columns are empty.

  3. Workflows in general

    • Any workflow that is not triggered directly by a user action (button, etc.) seems to treat my JS / Joined List columns as unsupported Experimental Code and gives me empty values.

So right now, the only way I can get the data out is:

Manually open the Data tab → go to Operaciones query → click Export → download CSV.

**
As you can guess, this is not optimal as i need this information downloaded on a daily basis
**
Any official clarification or known patterns would be really helpful. Right now the difference between “manual Export works” and “all automation paths return empties” is driving me crazy :sweat_smile:

Thanks in advance!

2

What’s most likely happening is that JS columns can only be evaluated client side. The reason for that is because running random JS server side could be dangerous and a big security risk due to potential SQL injection risks. In reality, the backend that Glide uses might not even be allowed to run uncontrolled JS. You might have to change your flow to write the JS column value to a basic column client side so your server side workflow can work with the written value instead of a computed JS value that probably isn’t allowed to run server side anyway.