🔒 Hide Sensitive Columns in the Interactive Report Export File (PDF / Excel)

-

🚩Introduction 

  • In Oracle APEX applications, reports may show both general and sensitive data like employee details, salary, or internal information. While this data can be shown on the screen, not all of it should be included when exporting to files like Excel or PDF for security and privacy reasons.

  • To manage this, we can control what gets exported using conditions like :REQUEST to hide sensitive columns during download while still showing them in the report. This helps protect confidential data, improves security, and ensures proper access control in Oracle APEX reports.

📑 Why It is Important to Control Export Columns in Oracle APEX Reports

In Oracle APEX applications, reports may show important data like employee details, salary, or other sensitive information. Sometimes, this data should be visible on the screen but should not be downloaded in Excel or PDF files.

Controlling export columns becomes important when:

  • Sensitive data like salary should not be included in downloads

  • Different users need to see different levels of information

  • Only necessary data should be exported

  • Data privacy and security need to be protected

  • Clean and simple export files are required

This helps keep data secure, avoids sharing of sensitive information, and gives better control in Oracle APEX applications.

👉 Use Case: Control Export Columns in Oracle APEX Reports

In Oracle APEX applications, reports often contain important data like employee details, department information, and salary. However, some of this information is sensitive and should not be included when exporting files like Excel or PDF.

In this blog, we will see how to control export columns in Oracle APEX so that only required data can be downloaded while sensitive information, like salary, is hidden. This helps protect confidential data, improves security, and provides a safer and more user-friendly reporting experience.

Step 1: 

In the Page Designer, create a region and select the type Interactive Report and select the query source for the report. In this blog, we are going to use the sample dataset table (EMP).

Step 2: 

Now we need to exclude the salary column from the export file like PDF or Excel. But we need to show those columns in the report. To do this, in the interactive report and go to the Salary column (in our case it is SAL column) and under the properties navigate to the Enable Users To option, select the Hide property. This is mandatory for this concept to work.

Step 3: 

In the interactive report and go to the Salary column (in our case it is SAL column) and under the properties navigate to the Server-side condition and select the Type as Expression and under the PL/SQL Expression, enter the following expression. This will exclude those columns from export file.


We are checking whether :REQUEST value is either 'PDF', 'XLSX' if it is then we are hiding that column from that export file, otherwise we will show those column in the report.
nvl(:REQUEST,'N') not in ('PDF','XLSX');

Step 4: 

Now save and run the page, you will see the report. Now click on the Download option from the Actions menu. A popup will be shown, in that select the download format like PDF or Excel. Now the column will be hidden from the export file.



🔥 Conclusion

Thus, in Oracle APEX, controlling export columns is an easy way to improve data security and manage reports better. Instead of exporting all fields, sensitive data like salary can be hidden during download. This helps prevent unwanted access, ensures only necessary information is shared, and keeps reports clean and useful. Overall, it makes the application more secure, controlled, and user-friendly.

Comments

Post a Comment

Popular posts from this blog

🔍 Extending Smart Search Filter for Multiple Regions

-
Image
🚩Introduction  In Oracle APEX, the Smart Search filter is a convenient feature that allows users to quickly search data in a Classic Report or Cards region without writing custom code. However, this functionality is limited to a single region , which can be restrictive when a page contains multiple regions that should respond to the same search input. In this tutorial, you will learn how to extend the Smart Search filter to work with multiple regions on the same page . We will implement a solution that allows one Smart Search input to drive filtering across multiple Classic Report ,Cards regions etc. By the end of this tutorial, you’ll have a clear, reusable approach for coordinating search behavior across regions, improving both usability and consistency in your Oracle APEX applications without breaking the declarative nature of APEX. 📑 Why Extending the Smart Search Filter Is Needed The built-in Smart Search filter in Oracle APEX works well when a page contains a single sear...
Read more

💡 Designing Dynamic QuickPicks in Oracle APEX

-
Image
🚩Introduction  Oracle APEX provides Quick Picks as a convenient way to allow users to populate page items with predefined values using a single click. While static Quick Picks are useful, real-world applications often require these values to be generated dynamically based on business rules, user roles, or underlying data. This blog explores how to implement Dynamic Quick Picks in Oracle APEX page items , enabling developers to build more intelligent, flexible, and user-friendly forms by driving Quick Pick values directly from database queries and runtime logic.  📑 Why Dynamic Quick Picks Are Needed   Static Quick Picks in Oracle APEX are useful for simple filtering, but Dynamic Quick Picks become essential when: Filter values must be generated at runtime based on current data, user role, or context Applications require data-driven filters instead of hardcoded values The same Quick Picks must adapt across multiple pages or regions Filter options depend ...
Read more

📌Track Active Tab switch in Region Display Selector without any plugins

-
Image
🚩Introduction  In Oracle APEX applications, Region Display Selector components helps to organize multiple regions efficiently. However, APEX does not provide a built-in declarative option to detect which tab is active when users switch between them, making it challenging to trigger conditional logic based on tab selection. This can be solved by creating the custom dyanamic action to capture the tab change. This approach enables dynamic actions like refreshing regions or executing custom logic whenever a tab becomes active, without requiring any plugins. 📑Why It is Essential to Track Tab Selection in Region Display Selector In APEX applications, pages often organize multiple regions under a Region Display Selector to separate content like Details, History, or Reports. While this improves layout, users actions on different tabs often require specific logic to run, such as refreshing a region, loading dynamic content, or updating page items. Without capturing which tab is active, de...
Read more