Skip to main content

Oracle APEX: Capture Text File Content in a Page Item

This blog demonstrates how to upload a text file in Oracle APEX and store its contents directly into a page item. Using JavaScript’s file reader API, the file is read on the client side without server upload. Once read, the content is dynamically assigned to a page item, allowing immediate use in forms or processes. 

We can approach this in two ways. First, the text file can have a structured format: the first row contains the name with a colon, the second row contains the email with a colon, and the third row contains the remarks with a colon. When the user uploads this kind of text file, the content is read and the corresponding values are set into the appropriate page items.

Second, we can simply upload any text file, and its entire content is set into a single APEX page item.

I created this blog for learning purposes, to explore the different options we can implement using APEX.

Step1: Create Apex Page with Following components.

P3_File Upload Item

P3_Name Text Field

P3_Mail Text Field

P3_Remarks Text Field

P3_Content Text Area

Submit1 Button

Submit2 Button

Step2: For the first button (submit1), add a Dynamic Action on Click and paste the following code

var fileInput = document.getElementById("P3_FILE");

if (fileInput && fileInput.files.length > 0) {

    var file = fileInput.files[0];

    var reader = new FileReader();

    reader.onload = function(e) {

        var lines = e.target.result.split(/\r?\n/);

        lines.forEach(function(line) {

            var parts = line.split(':'); // split label and value

            if(parts.length >= 2) {

                var label = parts[0].trim().toLowerCase();

                var value = parts.slice(1).join(':').trim(); // in case value has ":"


                if(label === 'name') {

                    $s("P3_NAME", value);

                } else if(label === 'email') {

                    $s("P3_MAIL", value);

                } else if(label === 'remarks') {

                    $s("P3_REMARKS", value);

                }

            }

        });

    };

    reader.readAsText(file, "UTF-8");

} else {

    alert("Please select a file first.");

}

From the above code, you can see that we are setting values to the page items based on the uploaded text document.

Step3: For the first button (submit2), add a Dynamic Action on Click and paste the following code

var fileInput = document.getElementById("P3_FILE");

if (fileInput && fileInput.files.length > 0) {

    var file = fileInput.files[0];

    var reader = new FileReader();

    reader.onload = function(e) {

        $s("P3_CONTENT", e.target.result);

    };

    reader.readAsText(file, "UTF-8");

} else {

    alert("Please select a file first.");

}

From the above code, all the content of the text file is set into the content page item

Step4: Save and run the application.

Demo_Application_Link









Comments

Post a Comment

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_...
Post a Comment
Read more

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 ...
Post a Comment
Read more

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 ...
Post a Comment
Read more