Bridge parent workflow trigger not passing through information to child workflow
Novice Bridge user, so apologies in advance if this is a elementary inquiry.
I am following the Engage '24 workflow for creating multiple rows from a single form entry and I'm stuck at the Child workflow. The Parent Trigger is set, but when I run the parent workflow, none of the parent data passes through to the child. I can't find anything indicating what I've missed to prevent the pass-through from completing successfully. Any guidance is appreciated.
Best Answer
-
Hi @Kat Capozzi
Thank you for providing this information! You're correct, they don't talk about how they configured the Child Workflow Module in the first (parent) workflow.
In order to pass through additional data (other than simply "how many times to run") you will need to specify what data to send in the Child Entity Values section.
This is because the array you're referencing only contains the values of the multi-select cell. You're not referencing the entire row, just that one cell.
That said! You can decide on a custom basis what else you'd like to pass through! You can even name the values whatever you'd like in that "Key #1" field, and that's how it will appear in the Child Workflow.
Have you tested adding any values in here?
Cheers,
GenevieveNeed more information? 👀 | Help and Learning Center
こんにちは (Konnichiwa), Hallo, Hola, Bonjour, Olá, Ciao!👋 | Global Discussions
Answers
-
Hi @Kat Capozzi
What are you referencing in the "Number of Runs" {{reference}}?
I can see you're referencing something from the Get Row Smartsheet returned data. That reference should be what's sending information to your second, child workflow as individual runs.
I wasn't at the 2024 Engage session, but my guess here is that they may be referencing a specific multi-select cell from the form submission, could that be correct?
Having the "Include Additional Object Value" checkbox Checked in the Get Row module would mean that a multi-select cell would be returned as an Array.
Then you can reference this "Values" array in your Child Workflow "Number of Runs" to tell it how many rows to create:
Can you confirm this is the Data Reference you used?
Then along with the Multi-Select Value, you can use the dropdown that says Child Entity Values to add more things to pass across (such as the Row ID or Sheet ID etc).
Let me know if this helped!
Cheers,
Genevieve
Need more information? 👀 | Help and Learning Center
こんにちは (Konnichiwa), Hallo, Hola, Bonjour, Olá, Ciao!👋 | Global Discussions
-
Hello @Genevieve P.!
Thanks for your response. The reference you show for the Number of Runs in Parent workflow child element is what I used. The error I am getting is when the child runs, The Sheet ID and other information that I believe should pass from the Parent WF to the Child does not. I'm following this video, which I found on another post here in the forum:
The full segment begins about @28:05, the child workflow begins @31:07, or there about. The presenter shows no steps for entering reference data into the child workflow trigger, but describes "pass through".
I have also consulted this Thread:
Which is where I found the above link, and I built a brand new workflow following this recommendation, but got the same result.
-
Hi @Kat Capozzi
Thank you for providing this information! You're correct, they don't talk about how they configured the Child Workflow Module in the first (parent) workflow.
In order to pass through additional data (other than simply "how many times to run") you will need to specify what data to send in the Child Entity Values section.
This is because the array you're referencing only contains the values of the multi-select cell. You're not referencing the entire row, just that one cell.
That said! You can decide on a custom basis what else you'd like to pass through! You can even name the values whatever you'd like in that "Key #1" field, and that's how it will appear in the Child Workflow.
Have you tested adding any values in here?
Cheers,
GenevieveNeed more information? 👀 | Help and Learning Center
こんにちは (Konnichiwa), Hallo, Hola, Bonjour, Olá, Ciao!👋 | Global Discussions
-
@Genevieve P. I did not. I have to say, I find it perplexing that step is not mentioned in this article, which is specifically for learning about the use of Child workflows. It seems an important step to leave out of a how-to?
Thank you for helping me along with this. I have much to learn about Bridge, and I find the support limited, but so far it has been invaluable in improved efficiency of my team!
Categories
- All Categories
- 14 Welcome to the Community
- Customer Resources
- 65.8K Get Help
- 425 Global Discussions
- 146 Industry Talk
- 485 Announcements
- 5.1K Ideas & Feature Requests
- 86 Brandfolder
- 151 Just for fun
- 73 Community Job Board
- 496 Show & Tell
- 33 Member Spotlight
- 2 SmartStories
- 306 Events
- 37 Webinars
- 7.3K Forum Archives