Table of Contents
CALL WITH ANOTHER TABLE
Category: Workflow / Internal
Description
This action calls another module or project, passes another table into the module/project, and can append the results.
Use cases
This action can be used to build data quality verification pipelines and can be used for custom reusable data quality checks.
Multiple Call with another table actions can be chained one after another and/or chained with the Verify data in another table action.
Action settings
| Setting | Description |
|---|---|
| Module/Project to run* | Select whether to call a module (within the current project), or an external project (.morph file), then select the module, or browse to the project file. |
| Pass table | Select another table in the current project to pass into the called module/project. |
| Return table | Select the table from the called module/project to return to the Call with another table action's dataset. |
| Append the returned dataset… | Check this option on to append the returned dataset to the input dataset of the Call with another table action. |
| Assign parameters | If values will be passed into the called module/project via parameters, select the parameter name to use, and the value* being passed in. |
* Setting can be specified using a parameter.
Remarks
The Call action, and the Call action paired with the Input action, are powerful ways to make your workflows more flexible.
When using the Input action in the called module or project, you can use the "Populate automatically" button to import the table being passed by the Call with another table to use as test data to build the rest of the module/project.
Examples
Calling a module (or project) with passing in another table via the Input action. Parameters are optional. A dataset is not being returned to the called module (or project).
Calling a module (or project) with passing in another table via the Input action. Parameters are optional. A dataset is returned to the called module (or project).
