Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 238 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 437 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Oracle Apex PL/SQL Dynamic Content issue

Hi,
In Oracle APEX 20.2, I have 2 parent regions, named Group and Ungroup, that uses type PL/SQL Dynamic Content. In the code, I used APEX's collapsible feature by copying the classes needed. Next, I created 2 buttons on a separate region, called Group and Ungroup, with Dynamic Actions. The Group button will show parent region Group and hide parent region Ungroup, while the Ungroup button will show region Ungroup and hide region Group.
The problem is, when I click Group button, it successfully shows parent region Group and hides parent region Ungroup, but when I click Ungroup button, it successfully hides parent region Group but fails to show parent region Ungroup.
After hours of testing and investigation, I found out that it could be caused by the same APEX collapsible classes I used in my code for the 2 parent regions. It seems the parent region Ungroup, is treated as a child region of parent region Group (even though Ungroup region is already a parent), and that's what's stopping the Ungroup region to be shown when I click Ungroup button.
Is there a way to avoid making Ungroup region be a child of Group region but still being able to the same APEX collapsible classes?
My last resort might be that I will no longer use the APEX classes for the Ungroup region.
Any ideas or suggestions are appreciated!
-Jazz
Answers
-
There is nothing here that allows us to help you. Without knowing exactly what you have done we are unable to identify the problem, let alone provide a solution.
You would have made better use of your time by demonstrating the issue in a shared workspace on apex.oracle.com so we could actually see it.
Why use PL/SQL Dynamic Content regions? They are very rarely necessary.
-
I'll take that into consideration (creating a shared workspace) next time in the future. For now, I separated the other region to be displayed in another page as a workaround.
The requirement was, for every time Table A has data, it should auto display those data, and I could do that through simple table reports, but I had to use PL/SQL Dynamic Content regions because the requirement had this specific UI I had to achieve.
After being able to customize the specific UI, and create a button that will redirect to another page, in PL/SQL Dynamic Content, I now have to create a Delete button which is in this separate issue
-
Let's forget about there being "separate issues" and deal with the whole problem, starting from scratch.
What is the "specific UI" that must be achieved?
Can you describe it and/or illustrate it with some formatted text, a diagram, or a simple mock-up on apex.oracle.com?