25.3.3 Importing Export Files

After you create Export files, you then import them into the target Oracle APEX instance.

After you upload export files, you have the option to immediately import them. You can also import them at a later time by navigating to the Export Repository.

Note that you cannot import an application created in a specific release into an earlier version. As a general rule, always import the application first and then the related files.

Tip:

To simplify the steps needed to deploy an application, Oracle recommends creating a custom application. See How to Create a Custom Application.

• Importing an Application Export
  Import a SQL or APEXlang application export on the Import page.
• Importing a Page
  Import a SQL page export on the Import page.
• Importing a Component
  Import a Component on the Import page.
• Re-importing an Application Containing Background Processes
  Learn about the workflow when re-importing an application with background processes.
• About Importing Applications and Application Groups
  Application groups are exported with an application, Application exports include a group ID, name, and comments.
• Importing Themes
  Import a Theme on the Import page.
• Importing Plug-ins
  Import the Plug-in on the Import page.
• Importing UI Defaults
  Import the UI Defaults on the Import page.
• Importing Team Development Feedback
  Import a Team Development Feedback Export on the Import page.
• Importing a REST Source Catalog
  Import a REST Source Catalog Export on the Import page.
• Importing an Application Blueprint
  Import an Application Blueprint on the Import page.

See Also:

• Understanding the Export and Import Process
• Managing Export Files from the Export Repository
• Exporting and Importing from a Command Line in Oracle APEX Administration Guide

25.3.3.1 Importing an Application Export

Import a SQL or APEXlang application export on the Import page.

Importing an APEXlang application export using App Builder has the following requirements:

• Oracle REST Data Services (ORDS) 26.1.1 or later - Your instance must be running Oracle REST Data Services (ORDS) 26.1.1 or later.
• REST Enabled Schema - At least one schema in the workspace must be REST enabled.

Failure to meet these requirements may an error to display.

Tip:

You can also import a SQL application export from the Export Repository. Navigate to the Export Repository and click the Import File and then go to step 3.

To import a SQL or APEXlang application export:

1. Navigate to the Import page:
   1. On the Workspace home page, select App Builder.
   2. On the App Builder home page, select Import.
2. On Import:
   1. Drag and drop, or navigate to the file.
   2. File Type - Indicate the type of export file to be imported.

      Select Application, Page or Component Export.

   3. File Character Set - Verify that the File Character Set is correct.
   4. Click Next to import the file.

   Once you upload a file, you have the option to import it. You can also import the file at a later time by navigating to the Export Repository.

3. On Import Application:
   1. Review the details.
   2. Parsing Schema - Select a schema. After the installation finishes successfully, this schema will be used to set the owner of the application.
   3. Build Status - Set the build status of the application. Options include:

      • Run Application Only - Users can only run an application.

        Selecting Run Application Only is an effective way to protect an application from modifications from other developers.

      • Run and Build Application - Users can run an application and developers can both run and edit an application.

      Tip:

      If you select Run Application Only, you can only change this setting after you import the application by signing in to Administration Services.
   4. Import As Application - Select how to import this application. You must specify an application ID that is unique across all workspaces. Options include:

      • Auto Assign New Application ID - A new application ID will be created for you.

      • Reuse Application ID XX From Imported Application - The application ID attached to the imported application will be used. When you import an application with the same ID as an existing application in the current workspace, the existing application is deleted and then replaced by the new application.

        Note:

        Importing an application that is currently locked by another user is not allowed. The user will be redirected to a notification page indicating that the application is locked.

      • Change Application ID - Specify a new application ID.

      You must specify an application ID that is unique across all APEX workspaces.

   5. Click Next.
   6. Subscriptions (conditional) - Only displays if the application contains subscribed components, plug-ins, or themes:
      • Subscription Mode - Select how subscriptions should be handled during the application import. Options include Strict, Ignore Errors, Remove, or Legacy. To learn more, see item Help.
      • Review subscription master application mappings. If applicable, review the Master Application ID from export file and To Application ID in the target workspace.
   7. Click Import Application.
      The file is imported. What appears next, depends upon the type of export. For example, the export could include Credentials, Remote Servers, or supporting objects.
4. If Credentials or Remote Servers are detected, follow the on-screen instructions to set up the Credentials or Remote Servers for your workspace.
5. If supporting objects are detected, the wizard guides you through the installation process. Click Install Supporting Objects and follow the on-screen instructions.
6. On the confirmation page, select the appropriate button:
   • Upgrade Application
   • Edit Application
   • Run Application

See Also:

Changing Application Build Status Set During Deployment in Oracle APEX Administration Guide

25.3.3.2 Importing a Page

Import a SQL page export on the Import page.

Note:

Importing an APEXlang page export using the App Builder, Import page is not available in this Oracle APEX release. Oracle recommends using SQLcl or SQL Developer for VS Code to import APEXlang application exports.

Tip:

You can also import an export file from the Export Repository. Navigate to the Export Repository and click the Import File and then go to step 3.

To import a SQL page export:

1. Navigate to the Import page:
   1. On the Workspace home page, select App Builder.
   2. On the App Builder home page, select Import.
2. On Import:
   1. Drag and drop, or navigate to the file.
   2. File Type - Indicate the type of export file to be imported.

      Select Application, Page or Component Export.

   3. File Character Set - Verify that the File Character Set is correct.
   4. Click Next to import the file.

   Once you upload a file, you have the option to import it. You can also import the file at a later time from the Export Repository.

3. On Import Page:
   1. Review the details.
   2. Import Into Application - Select the target application. You can import the page into the same application or into a different application.
   3. Click Import Page.

      Tip:

      When you import the page into the current application, Confirm Replace Page appears. To have the new page overwrite the existing page click Replace Page.

      Note:

      Importing a page into an application that is locked by another user is not allowed. The user will be redirected to a notification page indicating that the application is locked.
4. On the confirmation page, select the appropriate button:
   • Edit Application
   • Edit Page
   • Run Page

Note:

If you attempt to import a page that includes a shared component or a table not available in the target workspace, an error will occur because the import process will reference a non-existent component or table. To resolve this, ensure that the necessary components or tables are imported first.

25.3.3.3 Importing a Component

Import a Component on the Import page.

Tip:

You can also import an export file from the Export Repository. Navigate to the Export Repository and click Import File and then go to step 3.

To import a Component:

1. Navigate to the Import page:
   1. On the Workspace home page, select App Builder.
   2. On the App Builder home page, select Import.
2. On Import:
   1. Drag and drop, or navigate to the file.
   2. File Type - Indicate the type of export file to be imported.

      Select Application, Page or Component Export.

   3. File Character Set - Verify that the File Character Set is correct.
   4. Click Next to import the file.

   When you install components from a component import file into an application, the existing components are first deleted and then the new components are installed. If all statements are successful the install commits and the changes become permanent. If any errors are encountered, the install is rolled back, resulting in no permanent changes.

3. On Import Application Components:
   1. Import Into Application - Select the target application. You can import into the same application or into a different application.
   2. Click Next.
   3. Subscriptions (conditional) - Only displays if the import contains at least one subscribed component:
      • Subscription Mode - Select how subscriptions should be handled during the import. Options include Strict, Ignore Errors, Remove, or Legacy. To learn more, see item Help.
      • Review subscription master application mappings. If applicable, review the Master Application ID from export file and To Application ID in the target workspace.
   4. Click Import Application Components.

   You can import a component into the application you exported it from or into a different application.

   Tip:

   When you import components into the current application, Confirm Components appears. To have existing application components be replaced by components defined in the export file. click Replace Application Components.

   Note:

   Importing a component into an application that is locked by another user is not allowed. The user will be redirected to a notification page indicating that the application is locked.
4. On the confirmation page, select the appropriate button:
   • Edit Application
   • Edit Page
   • Run Page

Note:

Importing templates to different applications or workspaces is not currently supported.

25.3.3.4 Re-importing an Application Containing Background Processes

Learn about the workflow when re-importing an application with background processes.

Re-importing (or redeploying) an application which has background processes has a slightly different workflow compared to an initial Application Export import.

Tip:

You can also import an export file from the Export Repository. Navigate to the Export Repository and click the Import File and then go to step 3

To re-import an Application Export with background processes:

1. Navigate to the Import page:
   1. On the Workspace home page, select App Builder.
   2. On the App Builder home page, select Import.
2. On Import:
   1. Drag and drop, or navigate to the file.
   2. File Type - Indicate the type of export file to be imported.

      Select Application, Page or Component Export.

   3. File Character Set - Verify that the File Character Set is correct.
   4. Click Next to import the file.

   Once you upload a file, you have the option to import it. You can also import the file at a later time by navigating to the Export Repository.

3. On Import Application:
   On Install Application Wizard:
   1. Parsing Schema - Select a schema. After the installation finishes successfully, this will be used to set the owner of the application.
   2. Build Status - Set the build status of the application. Options include:

      • Run Application Only - Users can only run an application.

        Selecting Run Application Only is an effective way to protect an application from modifications from other developers.

      • Run and Build Application - Users can run an application and developers can both run and edit an application.

      Note:

      If you select Run Application Only, you can only change this setting after you import the application by signing in to Administration Services.
   3. Install as Application - Since you are importing an application export again, select Change Application ID.
   4. New Application - Enter the ID of the application from your first import.
   5. Click Import Application.

   A variation on the following message appears:

   The application to be replaced has page processes with background executions enabled. No process execution is running right now (9:45:24 PM).

   • Use the Disable Background Execution button to prevent new executions to be kicked off (by setting the Maximum Scheduler Jobs attribute to zero) and to return to this page.
   • Use the Replace Application button to install the imported application now. Running background executions will be terminated; waiting ones will be deleted.
4. Select the appropriate button:
   • Disable Background Execution - Prevents new executions from starting.
   • Replace Application - Install the imported application now. No background executions will run and any waiting executions will be deleted.
5. Install Supporting Objects - To continue and install supporting objects, enable Install Supporting Objects and click Next.
6. If Credentials or Remote Servers are detected, follow the on-screen instructions to set up the Credentials or Remote Servers for your workspace.
7. If supporting objects are detected, the wizard guides you through the installation process. Click Install Supporting Objects and follow the on-screen instructions.
8. On the confirmation page, select the appropriate button:
   • Install Summary
   • Edit Application
   • Run Application

See Also:

Changing Application Build Status Set During Deployment in Oracle APEX Administration Guide

25.3.3.5 About Importing Applications and Application Groups

Application groups are exported with an application, Application exports include a group ID, name, and comments.

When importing an application, the application import follows these rules:

• On import, an application uses an existing group if the ID matches.
• If no application group exists with the same ID on the target system, then application import looks for another group ID with the same name. If a name match is found, the application is imported with the ID corresponding to this application group name.
• If no ID or name matches existing application groups on the target system then a new application group is created. The new application group uses the application group ID if that ID is not used in that Oracle APEX instance. If the group ID is being used, then a new ID is generated.

25.3.3.6 Importing Themes

Import a Theme on the Import page.

To import a Theme Export:

1. Sign in to the APEX instance.
2. Navigate to the Import page:
   1. On the Workspace home page, select App Builder.
   2. On the App Builder home page, select Import.
3. On Import:
   1. Drag and drop, or navigate to the file.
   2. File Type - Select Theme Export.
   3. File Character Set - Verify that the File Character Set is correct.

   Once you upload a file, you have the option to install it. You can also import the file at a later time from the Export Repository.

4. To install the file, click Next.
5. On Import Theme:
   1. Import Into Application - Select the target application. You can import into the same application or into a different application.
   2. Click Next.
   3. Subscriptions (conditional) - Only displays if the imported theme subscribes to another theme:
      • Subscription Mode - Select how subscriptions should be handled during the import. Options include Strict, Ignore Errors, Remove, or Legacy. To learn more, see item Help.
      • Review subscription master application mappings. If applicable, review the Master Application ID from export file and To Application ID in the target workspace.
   4. Click Import Theme.

   Note:

   Installing a theme into an application that is locked by another user is not allowed. A validation error will appear when a locked application is selected.

25.3.3.7 Importing Plug-ins

Import the Plug-in on the Import page.

To import a Plug-in Export:

1. Sign in to the APEX instance.
2. Navigate to the Import page:
   1. On the Workspace home page, select App Builder.
   2. On the App Builder home page, select Import.
3. On Import:
   1. Drag and drop, or navigate to the file.
   2. File Type - Select Plug-in.
   3. File Character Set - Verify that File Character Set is correct.
   4. Click Next.

      Once you upload a file, you have the option to install it. You can also install the file at a later time from the Export Repository.

4. On Import Plug-in:
   1. Import Into Application - Select the target application. You can import into the same application or into a different application.

      When you install a plug-in into the current application, the new plug-in will overwrite an existing plug-in having the same plug-in name. If the installation succeeds, the installation of the plug-in becomes permanent. If any errors are encountered, the actions are rolled back, resulting in no permanent changes.

      Note:

      Installing a plug-in into an application that is locked by another user is not allowed. A validation error will appear when a locked application is selected.
   2. Click Next.
   3. Subscriptions (conditional) - Only displays if the import contains a subscribed a plug-in:
      • Subscription Mode - Select how subscriptions should be handled during the import. Options include Strict, Ignore Errors, Remove, or Legacy. To learn more, see item Help.
      • Review subscription master application mappings. If applicable, review the Master Application ID from export file and To Application ID in the target workspace.
   4. Click Import Plug-in.

25.3.3.8 Importing UI Defaults

Import the UI Defaults on the Import page.

You can install a UI Defaults Table Dictionary export into any schema provisioned in the workspace. When you install a Table Dictionary export, the old defaults will be overwritten. UI Defaults Attribute Dictionary imports replace any matching attribute definitions that are found but will not remove any existing attribute definitions that are not contained in the export. If the installation succeeds, the installation of the UI Defaults becomes permanent. If any errors are encountered, the actions are rolled back, resulting in no permanent changes.

To import a UI Defaults Export:

1. Navigate to the Import page:
   1. On the Workspace home page, click the App Builder icon.
   2. On the App Builder home page, click Import.
2. On Import:
   1. Drag and drop, or navigate to the file.
   2. File Type - Select UI Defaults.
   3. File Character Set - Verify that File Character Set is correct.
   4. Click Next.

      Once you upload a file, you have the option to install it. You can also install the file at a later time from the Export Repository.

3. To install an imported file, click Next.
4. Click Install UI Defaults.

25.3.3.9 Importing Team Development Feedback

Import a Team Development Feedback Export on the Import page.

To import a Team Development Feedback Export:

1. Sign in to the APEX instance.
2. Navigate to the Import page:
   1. On the Workspace home page, click the App Builder icon.
   2. On the App Builder home page, click Import.
3. On Import:
   1. Drag and drop, or navigate to the file.
   2. File Type - - Select Team Development Feedback.
   3. File Character Set - Verify that File Character Set is correct.
   4. Click Next.

      Once you upload a file, you have the option to install it. You can also install the file at a later time from the Export Repository.

4. To install an imported file, click Next.
5. Click Import Feedback.

25.3.3.10 Importing a REST Source Catalog

Import a REST Source Catalog Export on the Import page.

To import a REST Source Catalog Export:

1. Navigate to the Import page:
   1. On the Workspace home page, click the App Builder icon.
   2. On the App Builder home page, click Import.

   Tip:

   You can also access the Import page from the REST Source Catalogs page by selecting Import Catalog from the Tasks list on the right side of the page.
2. On Import:
   1. Drag and drop or navigate to the file.
   2. File Type - Select REST Source Catalog.
   3. File Character Set - Verify that File Character Set is correct.
   4. Click Next.

      Once you upload a file, you have the option to install it. You can also install the file at a later time from the Export Repository.

3. To install an imported file, click Next.
4. Click Import REST Catalog.

25.3.3.11 Importing an Application Blueprint

Import an Application Blueprint on the Import page.

Oracle APEX supports a Markdown-based blueprint format for Spec-Driven Development (SDD) with AI coding assistants. With SDD, the specification becomes the durable source of truth. The specification describes what the application should do, what the database means, and how users should work with the data. An AI assistant can use those specifications to generate an inspectable APEX application design artifact that can be reviewed before creating the application.

To import an Application Blueprint:

1. Navigate to the Import page:
   1. On the Workspace home page, select App Builder.
   2. On the App Builder home page, select Import.
2. On Import:
   1. Drag and drop, or navigate to the file.
   2. File Type - Indicate the type of export file to be imported.

      Select Application Blueprint.

   3. File Character Set - Verify that the File Character Set is correct.
   4. Click Next to import the file.

   Once you upload a file, you have the option to import it. You can also import the file at a later time from the Export Repository.

3. On Import Blueprint:
   1. Generative AI Service - Select a default Generative AI Service for this application. Generative AI Services can be configured from Workspace Utilities.
   2. Parsing Schema - Select a schema. After the installation finishes successfully, this will be used to set the owner of the application.
   3. Application ID - Specify a new application ID. The application ID is an integer value that identifies the application and must be unique within your APEX instance.

      Application IDs in the range of 3000 to 9000 are reserved for internal use by Oracle APEX.

   4. Click Import Application.
4. On the confirmation page, select the appropriate button:
   • Edit Application
   • Edit Page
   • Run Page