# Manual workflow parameter visible in parent Trigger Workflow, but not accessible inside child workflow

**URL:** <https://community.glideapps.com/t/manual-workflow-parameter-visible-in-parent-trigger-workflow-but-not-accessible-inside-child-workflow/87616>\
**Category:** Ask for Help\
**Created:** [August 26, 2026, 10:08am UTC](https://community.glideapps.com/t/manual-workflow-parameter-visible-in-parent-trigger-workflow-but-not-accessible-inside-child-workflow/87616 "2026-08-26T10:08:21Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shava\_Admin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/shava_admin/32/87767_2.png) [@Shava\_Admin](https://community.glideapps.com/u/Shava_Admin)\
**Post date:** [August 26, 2026, 10:08am UTC](https://community.glideapps.com/t/manual-workflow-parameter-visible-in-parent-trigger-workflow-but-not-accessible-inside-child-workflow/87616/1 "2026-08-26T10:08:22Z")

</div>

Hi everyone,

I’m trying to finish a bundle-sale workflow in Glide and I’m stuck on passing the Row ID of a newly-created Bundle row into a second workflow that processes selected Inventory items.

I’ll try to explain the setup clearly.

**What I’m trying to accomplish**

A user selects multiple Inventory items using a boolean column:

**Selected for Bundle = true**

They then press **Process Bundle Sale** and enter the overall bundle sale details, for example:

- Bundle Sale Price
- Platform
- Platform Fee
- Postage
- Sale Date
- Buyer Name
- Proof of Postage

When the sale is completed, I need Glide to:

1. Create one new row in the **Bundles** table.
2. Get the Row ID of that newly-created Bundle row.
3. Find all Inventory rows where **Selected for Bundle = true**.
4. Write the new Bundle Row ID into the **Bundle ID** column of every selected Inventory item.
5. Create an individual Sales row for each item.
6. Mark each Inventory item Sold and clear Selected for Bundle.
7. Allow a relation between Bundles.Row ID and Inventory.Bundle ID to identify the items belonging to that bundle.

At the moment the new Bundle row is created successfully, but its **Items in Bundle count remains 0** , because the selected Inventory rows are not receiving the new Bundle Row ID.

**Current parent workflow:**

**Process Bundle Sale**

The parent workflow currently does approximately:

**Accounts row**  
→ **Add Row to Bundles**  
→ show/edit the new Bundle screen  
→ set bundle sale values  
→ trigger some existing processing  
→ **Trigger Workflow: Process Selected Bundle Item**  
→ update Bundle status / show detail screen

The **Add Row to Bundles** action already uses:

**Result → Write row ID to → Current Bundle Row ID**

So the Row ID of the newly-created Bundle is being stored in a text column called **Current Bundle Row ID**.

**Child workflow:**

**Process Selected Bundle Item**

This is a separate Manual workflow.

I added a Manual trigger input:

**bundleRowID**  
Type: **Text**

This workflow contains:

**Manual Trigger**  
→ **Inventory Loop**  
→ Set Column Values on current Inventory row  
→ Add Row to Sales  
→ Set additional Inventory values

The Inventory Loop processes the selected Inventory rows.

**Passing the parameter from the parent**

Back in Process Bundle Sale, the **Trigger Workflow** action correctly recognises the parameter I created.

It shows:

**Process Selected Bundle Item**

and underneath it:

**bundleRowID**

I can therefore bind that input to the value containing the newly-created Bundle Row ID (Current Bundle Row ID).

So the parent appears to recognise the child workflow parameter correctly.

**Where I am stuck**

Inside the child workflow, I select:

**Set Column Values → current Inventory row → Bundle ID**

I want to set:

**Bundle ID = Trigger → bundleRowID**

In the value picker I can see these sources:

- Current date/time
- Unique identifier
- Device
- App
- **Trigger**
- Inventory

However, selecting **Trigger** only inserts/shows a generic Trigger value.

It does **not** open another level or expose the bundleRowID parameter.

I cannot find bundleRowID anywhere else in the value picker.

Searching for “bundleRow” only returns existing Inventory columns such as:

- Bundle Row ID Lookup
- Bundle Row ID Single
- New Bundle Row ID

Those are not the incoming workflow parameter.

**What Glide Support advised**

Glide Support advised that this should work using either a single workflow or parameters between workflows.

Their guidance for the two-workflow version was:

- Create a Manual trigger parameter in the child workflow, e.g. bundleRowID as Text.
- In the parent workflow, use Trigger Workflow and bind bundleRowID to the Add Row step’s new Row ID.
- Inside the child workflow loop, set Inventory.Bundle ID using the Trigger step’s bundleRowID input.

I have been able to do the first two parts.

The problem is specifically the final part: **I cannot access bundleRowID from the Trigger source inside Set Column Values.**

**Tables / relevant columns**

**Bundles**

- Row ID
- Bundle Name
- Bundle Sale Price
- Platform
- Platform Fee
- Postage
- Sale Date
- Proof of Postage
- Bundle Status
- Items in Bundle / relation to Inventory

**Inventory**

- Row ID
- Item Name
- Selected for Bundle
- Bundle ID
- Sold
- Status
- Final Sale Price
- Seller
- other item data

The intended relation is:

**Bundles.Row ID ↔ Inventory.Bundle ID**

**Expected result**

If a newly-created Bundle has Row ID:

ABC123

and two Inventory items are selected, I need the child workflow to produce:

**Inventory Item 1 → Bundle ID = ABC123**  
**Inventory Item 2 → Bundle ID = ABC123**

Then the Bundles relation should find those two items and **Items in Bundle should become 2**.

**Actual result**

The Bundle row is created successfully, but:

**Items in Bundle = 0**

and the selected Inventory rows do not receive the new Bundle’s Row ID.

**My question**

How do I reference the Manual trigger parameter **bundleRowID** inside a later **Set Column Values** action in the child workflow?

Should clicking **Trigger** expose bundleRowID underneath it?

If so, is there something I have configured incorrectly that would cause Glide to show only the generic **Trigger** value?

Alternatively, is there a better way to perform this entire operation in one workflow:

**Add Bundle row → Loop selected Inventory rows → set each current row’s Bundle ID to the newly-created Bundle Row ID**?

Any screenshots/examples of the exact value-picker configuration would be hugely appreciated.

Thank you!

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [August 27, 2026, 5:43am UTC](https://community.glideapps.com/t/manual-workflow-parameter-visible-in-parent-trigger-workflow-but-not-accessible-inside-child-workflow/87616/2 "2026-08-27T05:43:51Z")

</div>

> [@Shava\_Admin](#):
>
> Should clicking **Trigger** expose bundleRowID underneath it?

If there is just a single item passed via the trigger, selecting “Trigger” will target that item.  
If there are multiple items, then they are targeted via Trigger-\>Item.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [August 27, 2026, 5:45am UTC](https://community.glideapps.com/t/manual-workflow-parameter-visible-in-parent-trigger-workflow-but-not-accessible-inside-child-workflow/87616/3 "2026-08-27T05:45:36Z")

</div>

> [@Shava\_Admin](#):
>
> A user selects multiple Inventory items using a boolean column:
> 
> **Selected for Bundle = true**

What would you expect to happen if two or more users trigger this workflow at the same time?

---

<div class="post-metadata">

**Author:** ![Shava\_Admin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/shava_admin/32/87767_2.png) [@Shava\_Admin](https://community.glideapps.com/u/Shava_Admin)\
**Post date:** [August 27, 2026, 6:43am UTC](https://community.glideapps.com/t/manual-workflow-parameter-visible-in-parent-trigger-workflow-but-not-accessible-inside-child-workflow/87616/4 "2026-08-27T06:43:26Z")

</div>

Thanks Darren — that’s really helpful. So because my Manual trigger has only one Text input (bundleRowID), setting Inventory → Bundle ID = Trigger should use that bundleRowID value directly, correct?

---

<div class="post-metadata">

**Author:** ![Shava\_Admin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/shava_admin/32/87767_2.png) [@Shava\_Admin](https://community.glideapps.com/u/Shava_Admin)\
**Post date:** [August 27, 2026, 7:27am UTC](https://community.glideapps.com/t/manual-workflow-parameter-visible-in-parent-trigger-workflow-but-not-accessible-inside-child-workflow/87616/5 "2026-08-27T07:27:21Z")

</div>

Good point — in production I definitely wouldn’t want the loop to process every row where Selected for Bundle = true.

Inventory is user-owned, so I’d expect the loop filter to be something like:

Selected for Bundle = true  
AND Owner Email = triggering user’s email  
AND Bundle ID is empty

That way simultaneous bundle sales from different users should remain isolated.

Would you recommend passing the triggering user’s email into the Manual workflow as a second parameter alongside bundleRowID, then using both values in the loop filter?

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [August 27, 2026, 10:00am UTC](https://community.glideapps.com/t/manual-workflow-parameter-visible-in-parent-trigger-workflow-but-not-accessible-inside-child-workflow/87616/6 "2026-08-27T10:00:42Z")

</div>

> [@Shava\_Admin](#):
>
> So because my Manual trigger has only one Text input (bundleRowID), setting Inventory → Bundle ID = Trigger should use that bundleRowID value directly, correct?

Yes, correct.

> [@Shava\_Admin](#):
>
> Would you recommend passing the triggering user’s email into the Manual workflow as a second parameter alongside bundleRowID, then using both values in the loop filter?

Yes, that’s the right approach.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [September 3, 2026, 10:01am UTC](https://community.glideapps.com/t/manual-workflow-parameter-visible-in-parent-trigger-workflow-but-not-accessible-inside-child-workflow/87616/7 "2026-09-03T10:01:06Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.