Think APEX

Oracle APEX · Step-by-Step Guide Importing one Excel sheet is easy with the built-in wizard. Importing a workbook with related parent and child sheets — and keeping the keys straight — takes a bit more care. Here's the full pattern. Excel is still the undisputed king of business data. As Oracle APEX developers, we're frequently asked to build import utilities. While importing a single-sheet Excel file in APEX is straightforward using the built-in wizard or APEX_DATA_PARSER , things get trickier when a single workbook contains multiple worksheets with relational data — like a parent header and child lines. In this post, we'll parse a multi-sheet Excel file, assign separate database sequences for primary keys, maintain the parent-child relationship, and stage everything into APEX Collections for reporting. The Scenario A user uploads a single workbook containing two worksheets: Parent_Department — a single row defining the main departm...

Dynamic Report Introduction In many Oracle APEX applications, different reports require different SQL queries. Instead of hard-coding these queries into the application, users can store multiple SQL queries in a database table. These queries may contain bind variables (for example, :P_DEPTNO or :P_EMPNO ). When a user selects a report, the application automatically: Identifies the bind variables used in the selected SQL query. Dynamically generates input fields for those parameters. Prompts the user to enter the required values. Executes the query using the provided inputs. Refreshes the report with the filtered results. This approach allows a single report region to execute multiple dynamic queries without requiring any code changes. Step-by-Step Implementation Step 1 Create the QUERY_MASTER Table This table acts as our repository for SQL queries. We will...