Asset Dependencies Mapping
Workflow promotion requires mapping asset dependencies to the corresponding connections and datasets in the destination workspace.
The required mapping approach depends on where the workflow was created:
Workflow Type | What to Use |
|---|---|
Desktop workflow or Workflow Execution that references a Workspace Execution connection. | Connection Mapping |
Cloud workflow (Designer Cloud) that references a dataset. | Dataset Mapping |
These mappings ensure promoted workflows continue to run successfully in the destination workspace.
Why Dependencies Mapping is Important
Desktop workflows reference Workspace Execution connections by Connection ID, and those IDs are specific to the workspace where they were created. When a package is promoted, the source Connection ID might not exist in the destination workspace. So, without a mapping, the workflow fails after promotion.
Connection Mapping solves this by linking the source Connection ID to the correct target Connection ID, so the promoted workflow resolves to the right connection automatically at run time.
Cloud workflows don't use Workspace Execution connections, instead they use datasets. Dataset Mapping does the equivalent job for cloud workflows: it makes sure the datasets a promoted workflow reads from and writes to are correctly resolved in the destination workspace, including the connection and, if needed, the schema/table or file path.
Connection Mapping for Desktop Workflows
Connection Mapping lets you associate the source connection with the corresponding connection in the destination workspace. After the mapping is saved, promoted workflows automatically use the correct connection whenever they run in that workspace.
Where Can you Create Connection Mappings
You can create connection mappings in either location:
Fix Mappings while reviewing an incoming promotion request.
Connection Mappings management page.
Mappings are saved at the workspace level and can be reused for future promotions.
Create a Connection Mapping During Promotion
When you're reviewing an incoming promotion request and open Fix Mappings, if the workflow was authored on desktop, you'll see a Create a Connection Mapping modal with two fields:
Source connection: Each row shows the source Connection ID, and where available, the connection name, an icon, and when it was last updated.
Target connection: For each source connection, choose how to resolve it:
Select an existing connection from the dropdown.
Paste in a Target Connection ID directly.
Select Create New Connection create a new mapping.
You can map more than one source connection to the same target connection if that fits your setup.
Create a Connection Mapping Outside Promotion
You don't have to wait until you're reviewing a promotion request to set up mappings. You can create and manage connection mappings outside of the promotion process from the Connections Mapping page.
For complete details on creating connection mappings and their management, go to Manage Connection Mapping.
Mappings are saved at the workspace level, so once you've created one, it's automatically reused for future promotions involving that connection. There is no need to map it again unless something changes. Any mapping that already exists for a source connection will show up automatically in Fix Mappings, and reviewers can't edit it there. Mappings can only be changed from the Connections Mapping page.
What Happens When the Workflow Runs
Once a mapping is saved, it's applied automatically every time the workflow runs in that workspace.
Note
If the target connection later changes, you don't need to create a new mapping. The workflow will continue using the connection it is currently mapped to.
The user running the workflow needs access to the target connection. Mapping the connection doesn't automatically grant access to it, so make sure the right people or service accounts have permission to use the target connection.
Even if the user running the workflow doesn't have the target connection's credentials shared with them directly, the mapping will still work. The credentials are resolved at execution time. For more details, go to Credentials and Security.
Dataset Mapping for Designer Cloud Workflows
Designer Cloud workflows use datasets instead of Workspace Execution connection references.
During promotion, Dataset Mapping associates each input and output dataset with the appropriate dataset in the destination workspace. This ensures the promoted workflow reads from and writes to the correct data sources.
Prerequisites
You must have access to every dataset used by the workflow.
If you do not have the required permissions:
Ask the dataset owner to share the dataset with you.
Or, create the required datasets before continuing with the promotion.
Map Datasets During Promotion
At Fix Mappings, map each input and output dataset to the corresponding dataset in the destination workspace. Dataset mapping is required only the first time an asset is promoted through the SDLC process.
After the mappings are saved:
Future promotions of the same package reuse the saved mappings and automatically map datasets.
Only new or changed datasets require additional mapping.
This keeps later promotions faster while still giving you the chance to review anything that's actually different.
Credentials and Security
Connection mappings do not copy or share connection credentials. When a mapped workflow runs, credentials are resolved at execution time using the target connection. This allows administrators to manage connections separately from workflow promotion while maintaining appropriate security controls.