Skip to main content

Exporting Multiple APEX Applications in a Single ZIP File as an End User

This PL/SQL block allows end users to export multiple Oracle APEX applications simultaneously. It collects the selected application IDs, generates their export files, and packages them into a single downloadable ZIP file for convenience.

Step1: Create Classic Report with following query 

SELECT 

APEX_ITEM.CHECKBOX2(1, APPLICATION_ID, p_attributes => 'class="my_value"') AS SELECT_BOX,

    OWNER,

    WORKSPACE,

    APPLICATION_ID,

    APPLICATION_NAME,

    CREATED_BY,

    CREATED_ON,

    LAST_UPDATED_BY,

    LAST_UPDATED_ON

FROM APEX_APPLICATIONS;

Step2: Create Following Apex Page Items

Step3: Paste the following code in Function global declaration

$(document).ready(function () {

    $('.my_value').on('click', function () {

        var app_id = "";

        $('.my_value:checked').each(function () {

            app_id += $(this).val() + ",";     

        });

        app_id = app_id.substring(0, app_id.length - 1);

        $s('P4_SEL_APP_ID', app_id);

    });

});

When a checkbox is clicked in the report, the application IDs from the selected rows are stored in a page item as a comma-separated list.

Step 4: Paste the following PL/SQL code into a page process and configure it to run on button click.

declare

    l_files       apex_t_export_files;

    l_all_files   apex_t_export_files := apex_t_export_files();

    l_zip         blob;

    l_export      apex_data_export.t_export;

    l_original_id boolean := (:P4_ORIGIONAL_ID = 'Y');

    l_app_ids     apex_t_varchar2;

begin

    l_app_ids := apex_string.split(:P4_SEL_APP_ID, ',');

    for i in 1 .. l_app_ids.count loop

        l_files := apex_export.get_application(

                       p_application_id     => l_app_ids(i),

                       p_with_original_ids  => l_original_id,

                       p_with_date          => true,

                       p_with_comments      => true

                   );

        l_all_files := l_all_files multiset union all l_files;

    end loop;


    if l_app_ids.count > 1 or :P4_ZIPFILE = 'Y' then

        l_zip := apex_export.zip(p_source_files => l_all_files);

        l_export.content_blob := l_zip;

        l_export.mime_type    := 'application/zip';

        l_export.file_name    := case 

                                     when l_app_ids.count > 1 then 'apps_export.zip'

                                     else 'f' || l_app_ids(1) || '.zip'

                                 end;

        l_export.format       := 'zip';

        l_export.as_clob      := false;

    else

        l_export.content_clob := l_all_files(1).contents;

        l_export.mime_type    := 'text/plain';

        l_export.file_name    := 'f' || l_app_ids(1) || '.sql';

        l_export.format       := 'sql';

        l_export.as_clob      := true;

    end if;

    apex_data_export.download(p_export => l_export);

end;

Step5 : Save and Run the application.






Comments

Popular posts from this blog

APEX - Tip: Fix Floating Label Issue

Oracle APEX's Universal Theme provides a modern and clean user experience through features like floating (above) labels for page items.  These floating labels work seamlessly when users manually enter data, automatically moving the label above the field on focus or input.  However, a common UI issue appears when page item values are set Dynamically the label and the value overlap, resulting in a broken and confusing user interface. once the user focuses the affected item even once, the label immediately corrects itself and displays properly. When an issue is reported, several values are populated based on a single user input, causing the UI to appear misaligned and confusing for the end user. Here, I'll share a few tips to fix this issue. For example, employee details are populated based on the Employee name. In this case, the first True Action is used to set the values, and in the second True Action, paste the following code setTimeout(function () {   $("#P29_EMAIL,#P29_...

Building a Custom Debug Package for Oracle APEX Using PL/SQL

While developing Oracle APEX applications, debugging page processes and backend PL/SQL logic can be challenging—especially when values are lost between processes or execution flow is unclear.  Although DBMS_OUTPUT is useful, it doesn’t work well inside APEX runtime. To solve this, I built a custom PL/SQL debug Package that logs execution flow and variable values into a database table.  This approach helps trace exactly where the code reached, what values were passed, and whether a block executed or not - even inside page-level processes and packaged procedures Why a Custom Debug Package? Works seamlessly inside Oracle APEX page processes Persists debug information even after session ends Helps trace execution flow Captures runtime values Can be turned ON/OFF dynamically Does not interrupt business logic The Package consists of:- Debug Table                         -  Stores debug messages Sequence ...

Conditional Cell Editing in Oracle APEX IG

While browsing the Oracle APEX forum, I noticed a question from a user asking how to disable all other cells in an Interactive Grid row until the first cell has a value. In this blog, we will explore how to disable all other cells in an Interactive Grid row until the first cell contains a value. This approach helps enforce proper data flow, avoids incomplete or invalid records, and improves overall data integrity.  By implementing a simple client-side logic using JavaScript and Dynamic Actions, we can gain fine-grained control over row-level editing behavior in Oracle APEX. Step1: Create IG with static ID of EMP. Step2: Paste the following code in function global declaration. function setCellsToReadOnly()  { var grid = apex.region("EMP").widget().interactiveGrid("getViews", "grid"); if (!grid || !grid.model) { return; } var model = grid.model; model.forEach(function (record, index, id) { var meta = model.getRecordMetadata(id); var fields ...