Export an Oracle APEX 26.1 interactive grid for public sharing

If you have a reviewed dataset in an Oracle APEX interactive grid, first decide what you want to share: a report inside the APEX application, or a public copy of the data outside it. Saving a Public report and publishing a dataset serve different tasks.

This workflow uses the 26.1 documentation, whose release notes are dated July 2026. It covers sharing and export—not a claim that these capabilities are new in 26.1.

What the interactive grid provides

An interactive grid is a searchable, customizable report. Readers can change column order, sort the data and customize its presentation through column menus and the Actions menu. An editable grid additionally lets users add, modify and delete records; editing is not inherent to every interactive grid. See Oracle’s grid management guide and end-user guide.

For publication, use a reviewed, read-only dataset rather than exposing an operational editing interface. Prefer a dedicated source query containing only approved public fields; hiding columns for presentation should not be your publication review.

Choose the sharing route

Keep readers in APEX: Customize the grid, then use Actions → Report → Save As. Select Public, if available, enter a report name and click Save. Oracle says Public reports are visible to all application users, but developers must enable end users to save them; that capability is off by default. End-user save options also depend on application-level authentication and toolbar availability. These are saved-report settings, not a substitute for access controls.

A Public saved report does not by itself establish anonymous internet access. Authentication controls access to the application. Test the intended reader’s access separately.

If you need a link to a particular saved report, Oracle documents a Request value formed from IG[region HTML DOM ID]_ followed by the saved report’s static ID. Pages with multiple grids require region-qualified syntax, and opening links from outside the application may require the Deep Linking setting. Use the version-specific linking guide, rather than assuming a copied browser URL preserves your report selection.

Publish a separate public dataset: Export an approved snapshot, validate it, then publish the file. This is the useful route when readers should explore the data without entering your APEX application. Treat it as a separate publication with its own release date and update process.

Enable CSV downloads in APEX 26.1

If Download is unavailable, the application developer should check the grid configuration:

1. Open the page in Page Designer.
2. In Rendering, select the interactive grid region.
3. In the Property Editor, open Attributes.
4. Under Enable User To, turn Download on.
5. In the Download group, include CSV in Formats and check any download authorization scheme. If one is selected, it must evaluate to TRUE for the downloading user.
6. Set CSV Separator to a comma if the receiving workflow expects comma-separated data. Check CSV Enclosed By; Oracle’s default is double quotation marks.
7. Save the page.

Oracle also supports HTML, PDF and Excel downloads. Importantly, leaving the CSV separator blank can produce a comma or semicolon, depending on current NLS settings—Oracle’s locale-related settings. See Configuring Interactive Grid Download Formats.

Download rows, not report decoration

In the running application:

1. Review the selected report, filters and columns against the intended publication scope.
2. Choose Actions → Download, then CSV.
3. If Data Only appears, enable it to omit column groups, aggregates, highlights and control breaks.
4. If a Rich Text column exists and Strip Rich Text appears, enable it when plain text is appropriate.
5. Click Download.

Those options and their availability are documented in Oracle’s interactive-grid download instructions. Data Only removes report decoration; do not treat it as evidence that you exported the complete source dataset.

Check the file before publishing

For a fictional monthly service-request dataset, a useful structure would be:

Column	Purpose
district_code	Stable geographic identifier
month	Reporting period, such as 2026-09
request_category	Consistent category label
request_count	Numeric count; define whether blanks mean missing
source_url	Original public source
extracted_on	Snapshot date

Before upload, check that:

• The row count and total request_count match the approved extract.
• The file opens into the expected columns, including text containing commas or quotation marks.
• Identifiers retain leading zeros, dates are unambiguous and missing values have not become zeros.
• There are no subtotal rows or sensitive fields, and the table starts with its column headers. Preserve any necessary legal or classification notices in the accompanying publication notes rather than silently discarding them.

Use the CSV export checklist for a fuller file review.

TablePage accepts CSV, TSV, XLSX and XLS uploads and generates a public dataset page with a shareable link and filterable table. Upload only the approved public file. Then inspect the resulting table against your checked extract before sharing it. State the reporting period, source, snapshot date and planned update cadence so readers know exactly which version they are exploring.