Bridge - How to Retrieve Data from Multiple Child Runs Given the API Depreciations

Hello Team. Given the upcoming API depreciations, what is the recommended approach in Bridge to use the lastKey to get the full set of results in order to parse them when using the Call API to Smartsheet's API and needing to call it multiple times?

For example, if we have greater than 10,000 workspaces and we use the GET /workspaces call and retrieve the lastKey to make a additional calls, how do I get the full result set back to the parent to parse it? Currently I cannot retrieve data from Children that call themselves.

Example Flow:

Parent Workflow - uses GET /workspaces; responds with lastKey

- Conditional Junction: IS NOT EMPTY: lastKey: call Child workflow

Child Workflow (called for the first time) - uses GET /workspaces with the lastKey from the parent

I can pass the response of this workflow back to the parent

Child Workflow then calls itself because an additional lastKey is present.

I CANNOT pass this response back to the parent.

Requirement: get ALL workspace IDs and Names into a single variable to parse.

Find more posts tagged with

API and Developers

Bridge

Smartsheet API Deprecations

Accepted answers

All comments

Paul Newcome

I recently built something similar where I had to build on multiple child runs. You are on the right track wiht the IS EMPTY junction, but you need a javascript in place.

I would say a JS right before the junction though. You'll want one that basically appends all results to an existing list (existing list starts out blank for very first run). Pass that updated list along with the key through the child module back into the main workflow. Get workspaces with key passed in. JS appends new list to existing list. Junction checks for key. If key, repeat process. If no key, JS output should be full list.

Ryan Sides

Hey Paul, thanks for the help. But in this case, if a child calls itself, the parent cannot get the full results set back from the Nth run of the child (using JS to concat the list) . The parent will only return the result set of the 1st run of the child.

If the scenario is that the child does not call itself, I don't see how to loop through the junction again.

See what I mean?

Paul Newcome

Edit to add better screenshot.

If you keep passing the data through the child module and set the main workflow as the "child" workflow, it will loop.

Immediately after the trigger, I have an "Is Empty" conditional junction checking for a child entity value. If that is blank, it is my initial run. If it is false, then it is being fed by a child workflow.

Here is a very basic idea. Note that the workflow is set as the child workflow of itself. The two biggest pieces here are the JS that concatenates and passing data as child entity values.

You can pass the JS output as a child entity value which would then show up in the runtime data in the trigger section. You pass this entity into the JS as "existing list". You pass the new data in as "new list". JS Puts the two together as a single output. Pass that through the child workflow, and the next time around (if needed), the "existing list" now contains the previous "new list" as part of it so you can pass in the next "new list".

First junction determines whether this is the very first run or a subsequent run (key or no key).

Both paths will have a Get Workspaces call, but the one on the left would be a regular call, and the one on the right would incorporate the key for pagination.

Next you have your JS. Inputs would be "allWorkspaces" and "newList". The JS would create a blank list called "allWorkspaces" to start if the "allWorkspaces" input is blank or missing (initial run). It would then append the "newList" input which is the Get Workspaces call result to the end of the "allWorkspaces" list and provide that as its output.

Then you will have another junction checking if there is a key from this Get Workspaces call (meaning there is another page).

If there is a key, set up the child workflow module so that it is pushing to this same workflow one time, and pass the JS output as an entity.

You now have your "allWorkspaces" list as runtime data which is one of the inputs of the JS module.

Rinse and repeat until your Get Workspaces call doesn't produce a key (no more pages), and that final JS output should be all of your workspaces.

Sign in to join the conversation!

Quick Links

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, latest, sort, sortType, lookupSort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.