Passing a table from a subworkflow to the parent workflow | Community
Skip to main content
Level 2
January 24, 2025
Solved

Passing a table from a subworkflow to the parent workflow

  • January 24, 2025
  • 1 reply
  • 562 views

Hi,

 

I'm trying to call a subworkflow, that queries the nms:recipient table, based on varying variables passed into the sub workflow. This all works fine, but when returning to the parent workflow, I can't do much with it. Trying to do things like enrich it, or even something as basic as split it. I get errors generally relating to missing schema definitions, i.e.

XTK-170024 The temporary 'temp:subworkflow-jumpin' schema is not defined in the current context.

 

Is there any way I can tell it what it's being passed is the result of a query on nms:recipient, or is there some other configuration that's required?

Best answer by ccg1706

HI @raininglemons ,

 

You are facing this problem because Adobe Campaign doesn't recognize  the temporary schema 'temp:subworkflow-jumpin'. To secure that data from the subworkflow can be used in the parent workflow I share with you some possible steps to solve the issue:

-Be sure you select the nms:recipient schema at the end of the subworkflow so the parent workflow knows what type of data is coming out.

- Use an Enrichment activity to map the temporary data to the right schema (nms:recipient) after the subworkflow..

-Use JavaScript if you want to clean data and make it more usable, processing it as nms:recipient.

- Check the transitions and test how it works.

 

Kind regards, 

Celia

 

 

 

1 reply

ccg1706
Community Advisor
ccg1706Community AdvisorAccepted solution
Community Advisor
January 26, 2025

HI @raininglemons ,

 

You are facing this problem because Adobe Campaign doesn't recognize  the temporary schema 'temp:subworkflow-jumpin'. To secure that data from the subworkflow can be used in the parent workflow I share with you some possible steps to solve the issue:

-Be sure you select the nms:recipient schema at the end of the subworkflow so the parent workflow knows what type of data is coming out.

- Use an Enrichment activity to map the temporary data to the right schema (nms:recipient) after the subworkflow..

-Use JavaScript if you want to clean data and make it more usable, processing it as nms:recipient.

- Check the transitions and test how it works.

 

Kind regards, 

Celia