Import Flow
An exported flow can be imported into Designer Cloud.
Limitations
Nota
You cannot import flows that were exported before Release 6.8.
Nota
You cannot import flows into a version of the product that is earlier than the one from which you exported it. For example, if you develop a flow on free , which is updated frequently, you may not be able to import it into other editions of the product, which are updated less frequently.
Imported flows do not contain the following objects:
Nota
Depending on the import environment, some objects in the flow definition may be incompatible. For example, the connection type may not be valid, or a datasource may not be reachable. In these cases, the objects may be removed from the flow, or you may have to fix a reference in the object definition. After import, you should review the objects in the flow to verify.
Reference datasets
Nota
Reference dataset objects may refer to connections and parameters that are not specifically part of the flow being imported. These references must be remapped in the new project or workspace.
Samples
Connections
Sugerencia
When you import an exported flow, you can perform a remapping of the connections listed in the flow to connections in the new project or workspace. Details are below.
Imported datasets that are ingested into backend storage for Designer Cloud may be broken after the flow has been imported into another instance. These datasets must be reconnected to their source. You cannot use import mapping rules to reconnect these data sources. This issue applies to the following data sources:
Microsoft Excel workbooks and worksheets. See Import Excel Data.
Google Sheets. See Import Google Sheets Data.
PDF tables. See Import PDF Data.
Before You Begin
Dry-run import
Sugerencia
You can gather some of the following information by performing a dry run of importing the flow. In the Connections Mapping dialog, you can review the objects that need to be mapped and try to identify items that need to be fixed. Make sure you cancel out of the import instead of confirming it.
Import
Nota
If the exported ZIP file contains a single JSON file, you can just import the JSON file. If the export ZIP also contains other artifact files, you must import the whole flow definition as a ZIP file. For best results, import the entire ZIP file.
Import flow ZIP file
Steps:
Export the flow from the source system. See Export Flow.
Login to the import system, if needed.
Click Flows.
From the context menu in the Flow page, select Import Flow.
Sugerencia
You can import multiple flows (ZIP files) through the file browser or through drag-and-drop. Press
CTRL/COMMAND+ click orSHIFT+ click to select multiple files for import.Select the ZIP file containing the exported flow. Click Open.
Flow mappings
When you import a flow into a new project or workspace, you may need to remap the connections and environment parameters to corresponding objects from the import.
Finishing up
To complete the import process, click Confirm.The flow is imported and available for use in the Flows page.
Post-import
If you were unable to complete mappings through the dialog:
You may need to reconnect your imported datasets to data sources that are available in the new workspace or project. See Reconnect Flow to Source Data.
You may also need to reconnect your outputs. See Reconnect Flow to Outputs.
An administrator may need to create environment parameters for you. See Environment Parameters Page.
Samples are not included in an exported flow. Samples must be recreated in the new project or workspace. See Samples Panel.
Nota
If you have imported a flow from an earlier version of the application, you may receive warnings of schema drift during job execution when there have been no changes to the underlying schema. This is a known issue. The workaround is to create a new version of the underlying imported dataset and use it in the imported flow.