Skip to Main Content
Feature Request FR-4825
Product Area Application Builder
Status CLOSED

2 Voters

Independent Export/Import Utility for User-Saved Reports(public/private)

radwan.salamehh Public
· Mar 11 2026

Idea Summary

Enable the independent export and import of user-saved Interactive Reports and Interactive Grids (Private/Public) without needing to export the entire application so we can import them once the new updated app version is imported. 

Currently, user-saved reports are bundled within the full application export metadata. When deploying new application versions, these reports are often lost or become unusable if internal IDs change. We need a native utility in App Builder to export/import specific user-saved reports as standalone metadata files.

Use Case

  • Application Upgrades: When pushing an update to production, developers currently risk wiping out personalized report views that end-users rely on for their daily tasks.
  • Environment Migration: Moving specific user-saved configurations from a Development or Test environment to Production without moving the entire application structure.
  • Data Consistency: Maintaining user productivity by ensuring their saved filters, column selections, and sort orders are preserved even when the underlying application pages are modified.

Preferred Solution (Optional)

  • New App Builder Utility: Add a dedicated "Export/Import Report Definitions" wizard in the App Builder.
  • Developer Interface: Allow developers to select specific pages/All pages and specific saved reports from a list, then generate a small JSON/SQL file for that report's metadata.
  • ID Mapping: Include a feature to map the imported report metadata to the correct region IDs in the new application version to ensure the reports connect to the updated data source correctly.
This is a great idea! So much that we have already implemented it in a previous release of APEX.

Comments