Discussions
Categories
- 384.5K All Categories
- 2.5K Data
- 552 Big Data Appliance
- 1.9K Data Science
- 451.3K Databases
- 222.1K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 32 Multilingual Engine
- 560 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 561 SQLcl
- 4K SQL Developer Data Modeler
- 187.5K SQL & PL/SQL
- 21.4K SQL Developer
- 296.9K Development
- 1 Application Development
- 18 Developer Projects
- 140 Programming Languages
- 293.6K Development Tools
- 112 DevOps
- 3.1K QA/Testing
- 646.2K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 193 Java Community Process
- 106 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 21 Java Essentials
- 166 Java 8 Questions
- 86K Java Programming
- 81 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
- 206 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 531 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 178 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 236 Portuguese
Apex 5.0 Interactive Report without Maximum Row Count breaks Pivot
Hi guys,
I have accidentally found something interesting while playing with the fabulous pivot functionality of IRs in APEX 5.0. If you clear the Maximum Row Count in the IR's attributes, the report does not aggregate by the selected Row Column.
As an example, use the packaged app Opportunity Tracker and try the Leads Report. Set up a pivot like so ...
Pivot Columns: Lead
Row Columns: Territory Name
Functions: Count, Column Lead.
Looks great. Then edit the page and clear the Maximum Row Count. Run it again and it should be broken.
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
APEX Application Express 5.0.1.00.06
Cheers,
Michael
Answers
-
Michael,
Thank you for reporting the issue. It is a good find. Bug 21652393 is filed regarding the issue.
Regards,
Christina
-
No problems Christina.
Cheers,
Michael