Data flows and library nodes that you export from Data360 Analyze are saved as LNA files. You can import LNA files to any Data360 Analyze installation to share the contained data flows and library nodes with other users.
- From the Directory, select Import > Data Flows or Nodes:
- When prompted, select the LNA file that you want to import.
- In the Choose Folder dialog, select the folder to which you want to import the contents of your LNA, then click Choose.
The data flows and library nodes stored in the LNA file will be imported. If the import is successful, the imported data flows and any associated library nodes will be listed in your chosen folder in the Directory.
If there are any errors in the document that is being imported, an Import Issues dialog will notify you, giving you the option to continue or cancel the import. A common reason for seeing the Import Issues dialog is if the data flows or library nodes cannot locate all of their dependencies.
If the import fails, an Import Failed dialog will inform you that the process has not completed successfully. An import will most commonly fail if the version of Data360 Analyze used to export the file is more recent than the version you are running, or if you attempt to import an unsupported file type.
If there are any import conflicts, i.e. you are importing a document to a folder where there is already a document with the same name or ID, you can choose to overwrite the original document or select a different target folder for the import, see Import conflicts.
If you choose to overwrite a document with a document with the same ID, the imported document will inherit any permissions previously set on the original document.
See also: Importing legacy documents
Data flows and library nodes can be exported from the Directory in order to share them with others.
Note: When exporting a data flow with dependencies, this will include any run property sets that have been defined on the data flow. However, the export will not include any referenced run property sets (where one run property set inherits from another run property set). If exported and imported into the same system, where the referenced run property set exists, then this reference will still work. However, when importing into other systems where the referenced run property set does not exist, the parent run property set will need to be recreated and the data flow will need to be updated to use it.
- Select the items that you want to export and choose Export from the menu in the Details panel:
You can select multiple items by holding down the Ctrl key while selecting items. Note that it is not currently possible to export a folder.
Holding down the Shift key will select a range of items.
- The Export Documents dialog will appear, prompting you to choose whether to include dependencies in your export:
Dependencies are the library nodes which are used inside your chosen data flows and library nodes, and will be required by whoever imports your documents in order to open them in another Data360 Analyze installation. You should choose to include these dependencies, unless you know that they will be available on any Data360 Analyze installation into which your export file will be imported.
Your documents will be exported to a single LNA file, which can then be imported into another Data360 Analyze installation.