mirror of
https://github.com/ToolJet/ToolJet
synced 2026-04-24 06:57:40 +00:00
61 lines
2.8 KiB
Markdown
61 lines
2.8 KiB
Markdown
|
---
|
||
|
|
id: importing-exporting-applications
|
||
|
|
title: Import and Export Applications
|
||
|
|
---
|
||
|
|
|
||
|
|
This documentation explains the process of exporting and importing applications in ToolJet.
|
||
|
|
|
||
|
|
<div style={{paddingTop:'24px', paddingBottom:'24px'}}>
|
||
|
|
|
||
|
|
## Exporting Applications
|
||
|
|
|
||
|
|
- Navigate to the dashboard.
|
||
|
|
- Click on the settings icon located in the top right corner of the application.
|
||
|
|
- Click on the **Export app** button.
|
||
|
|
|
||
|
|
<div style={{textAlign: 'center', marginBottom:'15px'}}>
|
||
|
|
<img className="screenshot-full" src="/img/v2-beta/app-builder/import-export-apps/export-app-button-v2.png" alt="Export App Button" />
|
||
|
|
</div>
|
||
|
|
|
||
|
|
- If you select `Export All`, all the versions of the application will be exported in JSON format. If you select `Export selected version`, only the selected version will be exported in JSON format.
|
||
|
|
- Ticking the `Export ToolJet table schema` checkbox will also export the related ToolJet Database table schemas with your application. In this case, when you import the application in a workspace, the related ToolJet Database tables will also be created.
|
||
|
|
|
||
|
|
|
||
|
|
<div style={{textAlign: 'center', marginBottom:'15px'}}>
|
||
|
|
<img className="screenshot-full" src="/img/v2-beta/app-builder/import-export-apps/export-options-v2.png" alt="Export App Options" />
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div style={{paddingTop:'24px', paddingBottom:'24px'}}>
|
||
|
|
|
||
|
|
## Importing Applications
|
||
|
|
|
||
|
|
- Navigate to the dashboard.
|
||
|
|
- Click on the ellipses on the **Create new app** button and select `Import`.
|
||
|
|
|
||
|
|
<div style={{textAlign: 'center', marginBottom:'15px'}}>
|
||
|
|
<img className="screenshot-full" src="/img/v2-beta/app-builder/import-export-apps/import-button-v2.png" alt="Import App Button" />
|
||
|
|
</div>
|
||
|
|
|
||
|
|
- After clicking on `Import`, choose the relevant JSON file that you previously downloaded during the application export process.
|
||
|
|
|
||
|
|
|
||
|
|
<div style={{textAlign: 'center', marginBottom:'15px'}}>
|
||
|
|
<img className="screenshot-full" src="/img/v2-beta/app-builder/import-export-apps/select-app-to-import.png" alt="Select App To Import" />
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
## Module Behavior During Application Import and Export
|
||
|
|
|
||
|
|
**Import**:
|
||
|
|
|
||
|
|
- When you import an application, the platform automatically checks for any existing modules with matching names in your workspace or instance. If a module with the same name already exists, the imported application connects to the existing module, avoiding duplication.
|
||
|
|
- However, if no matching module is found, the platform creates a new module from the imported JSON file.
|
||
|
|
- This approach ensures that your application imports smoothly while maintaining consistency and preventing redundant modules.
|
||
|
|
|
||
|
|
**Export**:
|
||
|
|
|
||
|
|
- When you export an application, all associated modules linked to the application are automatically included in the export.
|
||
|
|
- This ensures that any reusable components or features built as modules are preserved and can be seamlessly imported along with the app into any other workspace.
|