Import Project Table

Description

Copies data from a table in a different project into the current project. The inverse of Export Project Table — pulls rather than pushes.

Useful when a consolidation project sources from many operational projects, or when reference data is centralized in one project and read by others. The source project must grant this project a Read data share.

Data Sharing Management

Before you can import a table from another project, that project has to let this one read it. Open the source project’s Home tab, and under Data Sharing Management click New Data Share, select this project, tick Read under Allowed Operations, and click Add Data Share. See Sharing Data Between Projects.

The step runs as this project’s own identity, so a run works through the share whoever starts it.

Import External Project Table

Read From

Select the Source Project and Source Table from the drop downs.

Write To

Target Table

The target selection for imports is limited to tables only since views do not contain underlying data.

Dynamic Option

The Dynamic option allows specification of a table using text, including variables. This is useful when employing variable driven workflows where table and view references are relative to the variables specified.

An example that uses the current_month variable to dynamically point to target table:

legal_entity/inputs/{current_month}/ledger_values

Note

If the table does not exist it will be created dynamically when the import process runs

Static Option

When a specific table is desired as the target for the import, leave the Dynamic box unchecked and select the target Table.

If the target Table does not exist, select the Create new table button to create the table in the desired location.

Table Explorer is always avaible with any table selection. Click on the Table Explorer button to the right of the table selection and a Table Explorer window will open.

Empty source table

If the source table has no rows when the step runs, the import finishes with a warning that the source was empty rather than a silent success — so an unexpectedly empty target is easy to spot. Most often this means the source project’s workflow had not yet built that table; make sure the source is populated (and, for scheduled runs, ordered to run first) before the import.

Deleting a source table

The source table you read from is treated as in use by this step. If you try to delete it, PlaidCloud shows the reference and makes you confirm a force-deletion — ticking Force the delete of the table? and choosing Force Deletion — rather than a plain delete, even when the import step lives in a different project that shares the data. In that cross-project case the warning lists the reference without naming the other project’s step, since you may not have access to it.