# Computed values not saving into new rows via workflow

**URL:** https://community.glideapps.com/t/computed-values-not-saving-into-new-rows-via-workflow/84672
**Category:** Ask for Help
**Created:** [September 30, 2025, 11:33am UTC](https://community.glideapps.com/t/computed-values-not-saving-into-new-rows-via-workflow/84672 "2025-09-30T11:33:22Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![bazd](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/bazd/32/91091_2.png) [@bazd](https://community.glideapps.com/u/bazd)
#### Post date: [September 30, 2025, 11:33am UTC](https://community.glideapps.com/t/computed-values-not-saving-into-new-rows-via-workflow/84672/1 "2025-09-30T11:33:22Z")

</div>

Hi all, I’m building a manager-focused planning app.

I have a workflow triggered by a button (“Run & Save”) that:

1. Runs on the current **Sales Metrics** row.
2. Does a **Set Column Values** step to stage a computed value (`Prospecting % Final`, an IF/THEN/ELSE number, into a plain number column called `Snapshot Staging (num)`).
3. Then creates a **New Row in another table** (Plan History), where I map `Prospecting % (snapshot)` in Plan History = `Snapshot Staging (num)`.

When I test in the workflow editor (clicking **Run** inside the builder), the value populates fine.  
When I press the **Run & Save button in the live app** , the new row is created, but `Prospecting % (snapshot)` is always **blank**.

Things I’ve already tried:

- Replacing the computed field with a staging Number field.
- Adding a helper Math column to coerce the % into a number.
- Switching the target column to Text.
- Confirmed the staging column itself _is_ populated before the Add Row runs.
- Mapping constants (like 999) _do_ show up in the new table, so the workflow step is firing.

So it seems the issue is with timing / computed → Add Row mappings not surviving at runtime.

**Question:**  
How can I reliably pass a computed number from one table into a new row in another table when creating that row in a workflow? Is there a pattern (e.g. RowID update, relation + Set Column Values, or a known timing workaround) that avoids the blank values?

Thanks in advance!

---

<div class="post-metadata">

### Author: ![Swift\_Struck\_24](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/swift_struck_24/32/91605_2.png) [@Swift\_Struck\_24](https://community.glideapps.com/u/Swift_Struck_24)
#### Post date: [September 30, 2025, 11:57am UTC](https://community.glideapps.com/t/computed-values-not-saving-into-new-rows-via-workflow/84672/2 "2025-09-30T11:57:22Z")

</div>

Hi there, the most reliable to ensure data from computed columns is loaded in a workflow is to use wait for conditions to ensure you computed columns are not empty.

Hope this helps 🙂

---

<div class="post-metadata">

### Author: ![bazd](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/bazd/32/91091_2.png) [@bazd](https://community.glideapps.com/u/bazd)
#### Post date: [October 1, 2025, 8:19am UTC](https://community.glideapps.com/t/computed-values-not-saving-into-new-rows-via-workflow/84672/3 "2025-10-01T08:19:37Z")

</div>

> [@Swift\_Struck\_24](#):
>
> Hi there, the most reliable to ensure data from computed columns is loaded in a workflow is to use wait for conditions to ensure you computed columns are not empty.

thanks!