Previous Next JavaScript must be enabled to correctly display this content

## 25.3.2.4 Exporting an Application Page

Move or copy a single application page by exporting it. You can export or page from the Export page or from Page Designer.

WARNING:

Exporting and importing a single page to a different system is an advanced deployment technique with the following restrictions:

- Both systems have to have the same application ID and workspace ID.
- Both systems have to have the same IDs for Shared Components.
- If the page references new or updated Shared Components, those have to be exported and imported first.

If these restrictions are not fulfilled, the import will fail.

- Exporting an Application Page from the Export Page
  Move or copy a single application page by exporting it from the Export Page.
- Exporting an Application Page from Page Designer
  Move or copy a single application page by exporting it from Page Designer.

Parent topic: Creating Export Files

### 25.3.2.4.1 Exporting an Application Page from the Export Page

Move or copy a single application page by exporting it from the Export Page.

To export a page from the Export page:

1. Navigate to the Export page:
   1. On the Workspace home page, select App Builder.
   2. On the App Builder home page, select Workspace Utilities.
   3. Click Export.

      The Export page appears.

      Tip:

      You can also access the Export page by selecting the application, Export/Import, and then Export.
2. Click the Page tab.

   Configure the Export Page attributes.

3. Application - Select the application.
4. Page - Identify the page you wish to export. You can select only one page for export at a time..
5. Format - Select the format for the export file. Options include:
   - SQL - Creates a readable script file with a `.sql` extension.
   - APEXlang - Creates a human-readable and modifiable version which is delivered as a zip file. APEXlang exports are optimized for AI generation, human readability, and source control management systems.

   The attributes that appear next depend upon the selected Format.

6. If Format is SQL:
   1. Format - Select SQL.
   2. Split into Multiple Files - Select this option to export separate SQL files for the page, shared components, and so forth. Available options include:

      - On - Export as a ZIP archive with separate SQL files.

        To learn more about the Zip archive, see Splitting Export Files into Separate SQL Scripts.

      - Off - Export as a single SQL file for the page.

   3. Original IDs - Specify whether the export file should contain the application component IDs as of now or as of the last import of this application. Options include:

      - On - Include the IDs as of the last import.

      - Off - Include the current IDs of the components.

      Using Original IDs can be beneficial for various purposes, including:

      - Readable Format: Simplify comparisons between different versions of app components and pages. Minimize changes to version controlled export files.
      - Shared Component Subscriptions: Ensure subscribed components stay linked to a source app when it is replaced with an updated version.
7. If Format is APEXlang - Select APEXlang.
8. Audit Information - Specify the audit information to include in the export file. Audit information includes the Created By User, Created On Date, Changed By User and Changed On Date. Options include:
   - None - (Default) No audit information is included.
   - Names and Dates - Include names and dates in all audit information.
   - Dates Only - Only include date information and exclude user details.
9. As of - Specify a time in minutes to go to back to for your export. This option enables you to go back in time in your application, perhaps to get back a deleted object.

   This utility uses the `DBMS_FLASHBACK` package. Because the timestamps to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version for which you are looking. The time undo information is retained and influenced by the start up parameter `UNDO_RETENTION` (the default is three hours). However, this only influences the size of the undo table space. While two databases may have the same `UNDO_RETENTION` parameter, you are able to go back further in time on a database with fewer transactions because it is not filling the undo table space, forcing older data to be archived.

10. File Character Set - Identifies the character set in which the export file will be encoded.
11. Click Export .
12. Import the Page Export into the target instance.

See Also:

Importing a Page

Parent topic: Exporting an Application Page

### 25.3.2.4.2 Exporting an Application Page from Page Designer

Move or copy a single application page by exporting it from Page Designer.

To export a page from Page Designer:

1. View the page to be exported in Page Designer:
   1. On the Workspace home page, select App Builder.
   2. Select an application.
   3. Select a page.
      Page Designer appears.
2. On the Page Developer toolbar, click the Utilities menu () and then select Export.
3. On Export Page, configure the following:
   1. Export Application, Format - Select the format for the export file. Options include:
      - SQL - Creates a readable script file with a `.sql` extension.
      - APEXlang - Creates a human-readable and modifiable version which is delivered as a zip file. APEXlang exports are optimized for AI generation, human readability, and source control management systems.

      The attributes that appear depend upon the selected Format.

   2. Split into Multiple Files - Select this option to export separate SQL files for the page, shared components, and so forth. Available options include:

      - On - Export as a ZIP archive with separate SQL files.

        To learn more about the Zip archive, see Splitting Export Files into Separate SQL Scripts.

      - Off - Export as a single SQL file for the page.

   3. Original IDs - Specify whether the export file should contain the application component IDs as of now or as of the last import of this application. Options include:

      - On - Include the IDs as of the last import.

      - Off - Include the current IDs of the components.

      Using Original IDs can be beneficial for various purposes, including:

      - Readable Format: Simplify comparisons between different versions of app components and pages. Minimize changes to version controlled export files.
      - Shared Component Subscriptions: Ensure subscribed components stay linked to a source app when it is replaced with an updated version.
   4. Audit Information - Specify the audit information to include in the export file. Audit information includes the Created By User, Created On Date, Changed By User and Changed On Date. Options include:
      - None - (Default) No audit information is included.
      - Names and Dates - Include names and dates in all audit information.
      - Dates Only - Only include date information and exclude user details.
   5. As of - Specify a time in minutes to go to back to for your export. This option enables you to go back in time in your application, perhaps to get back a deleted object.

      This utility uses the `DBMS_FLASHBACK` package. Because the timestamps to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version for which you are looking. The time undo information is retained and influenced by the start up parameter `UNDO_RETENTION` (the default is three hours). However, this only influences the size of the undo table space. While two databases may have the same `UNDO_RETENTION` parameter, you are able to go back further in time on a database with fewer transactions because it is not filling the undo table space, forcing older data to be archived.

   6. File Character Set - Identifies the character set in which the export file will be encoded.
4. If Format is APEXlang:
   1. Audit Information - Specify the audit information to include in the export file. Audit information includes the Created By User, Created On Date, Changed By User and Changed On Date. Options include:
      - None - (Default) No audit information is included.
      - Names and Dates - Include names and dates in all audit information.
      - Dates Only - Only include date information and exclude user details.
   2. As of - Specify a time in minutes to go to back to for your export. This option enables you to go back in time in your application, perhaps to get back a deleted object.

      This utility uses the `DBMS_FLASHBACK` package. Because the timestamps to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version for which you are looking. The time undo information is retained and influenced by the start up parameter `UNDO_RETENTION` (the default is three hours). However, this only influences the size of the undo table space. While two databases may have the same `UNDO_RETENTION` parameter, you are able to go back further in time on a database with fewer transactions because it is not filling the undo table space, forcing older data to be archived.

   3. File Character Set - Identifies the character set in which the export file will be encoded.
5. Click Export .
6. Import the Page Export into the target instance.

See Also:

Importing a Page

Parent topic: Exporting an Application Page