This feature is only available on r330 and later, and LTS15 and later.
Users on Enterprise plans and above.
While export and import brings a vast majority of context within applications, it doesn't bring everything, and there may be some work required following an import to make an application functional.
Added Features in V2
Machines
Machines will be included on import (although their mappings and data sources won't be).
Table Queries and Aggregations
Table Queries and aggregations will not create duplicates upon every import. They will work similarly to connector functions by successfully merging with the previous setup on that instance.
Tables
Archived table fields will not be included with their parent tables when they are exported.
Linked record table field types will export to infinite depth, not just one layer of linking.
Analytics
Previously, changes to analytics were not reflected in imported apps. Now, apps will import analyses alongside them as new analyses, so changes are preserved.
App analyses (on completion data) will not be be exported if they are referencing an app that is not included in the import. They will be clearly blank in the App Editor.
App Version Comparison
App version comparisons will work after importing a new version to an existing app- in the previous feature, it does not work.
It will only work for new versions imported after the launch of this feature- forward-facing only.
Assets that aren't moved
Not all assets that can be referenced within an app or automation are automatically moved when that asset is exported. These are cases that need to be addressed following import.
Approval types
Approval types are not moved during export, and all approvals are removed from new apps on import.
Users
Users are not moved during export. Any users that have been assigned in app permissions, or referenced within app logic will need to be replaced.
App transitions
If one application transitions to another app, that Transition may be removed during export and import.
If App A has a transition to App B and they are both in an app group that is exported, then transitions will be maintained. If only App A or App B is exported, that transition will break.
Station and interface configuration
Any references to stations, interfaces, machine data sources and edge devices will be broken upon import/export.
Requires some configuration
Connector environments
Connector Environments (and authentication) details are not moved when connectors are moved between sites. Authentication will need to be redone after a connector is moved between sites.
Authentication tokens stored in custom headers on the connector or a function will be transfered.
Approvals
Approvals will be removed from an application on Export/Import. These must be reconfigured in the target instance.
App permissions
App Permissions will be removed from an application on Export/Import. These must be reconfigured in the target instance.
Data that is not moved
Version history
Application version history is not moved on app export. Only a single application Version will be moved between instances.
Applications can be imported into an existing application, adding a version to the version history.
Any completion or table data
The data stored within Tables and Completions is not moved when an application is exported and imported.
Activity feed records
The activity feed data associated with an asset, or any of its depencies are not moved on export and import.
.gif)