Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 239 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
- 546 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K 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
- 442 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
gReport.data.view('DETAIL');

What is equivalent of javascript call "gReport.data.view('DETAIL');" in version 5.0?
BR,ivan
Answers
-
Bumping because I'm curious myself. This presentation from Karen seems to mention everything but.
https://thtech.files.wordpress.com/2015/03/apex5_ir_features.pdf
-
This functionality has been made private with the move to a jQuery UI widget. That whole paper's part on JS can actually simply be disregarded. The only public functionality is "refresh" and reading some (useless to us) options. And well, these last 2 sentences actually:
Developers that have customizations that rely on the old IR JavaScript must review and update their code.
Well, not much to review since it'd all be broken and near unfixable anyway.
Again, it is not expected that customized use of the IR JavaScript functions will be supported. Developer beware …
Yeah, well. I don't think anybody expected wild things anyway.
------
This happened to most other functionality which you could previously access through gReport. And there is no 'clean' way to fix this right now (call a method on the widget). Much like "paginate": https://community.oracle.com/message/13017402#13017402
You can actually do the same as I did there bar some changes. See here ==> https://apex.oracle.com/pls/apex/f?p=90922:9:0::::: (set ir view mode)
The other thing you can do:
1) make sure the detail button is visible (option set to yes in the designer)
2) emulate a click on it, along the lines of
apex.jQuery("#YOUR_IR_SELECTOR button.a-IRR-button--views[data-view=details]").click()
I'd really like to lament not having more public functions available but that's where it stands right now. I understand how gReport was probably used all over the place and how some things were exposed that maybe shouldn't have, but right now I feel we've lost some power. I don't see how having to do these click events is in any way more safe than having used gReport. I actually feel disappointed. I'd not expect to have everything opened up publicly, though here was a chance to do so properly and in a controlled way instead of boxing everything in. Oh well, must be me.