Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 238 Big Data Appliance
- 1.9K Data Science
- 450.2K 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
- 154 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
Feature request: Shared User Defined Reports

It would be great if SQL Developer supported a convenient way to share user defined reports with other people on your team.
My team is using git to share exported reports. There do not appear to be any tools within SQL Developer to help keep reports in sync with a file on the PC.
Best Answer
-
Hi,
It would be great if SQL Developer supported a convenient way to share user defined reports with other people on your team.
Then it is great, because that feature already exists. π
Ever noticed these?
But first, you must convert your reports into individual XML extensions. That's easy, and well explained in the following documents:
- https://github.com/PhilippSalvisberg/sqldev/blob/main/workshop/010_create_report_xml_extension/README.md#create-report-as-xml-extension
- https://github.com/oracle-samples/oracle-db-examples/tree/main/sqldeveloper/extension/xml/individual#sql-developer-examples
Don't forget to nest the main
<display>
element of your reports inside a<folder>
element in order to group them into folders under Shared Reports. (See the example in the end of this post.)Once you have done that, nothing prevents you from loading individual XML extensions from your local Git repository, making it possible to synchronize with your project's remote Git repository by just pulling from that remote, then restarting SQL Developer.
(It takes a bit of manual configuration work: each individual XML extension must be configured in Preferences. But once this is done, it just works. Restarting SQL Developer is required for changes to become available, though.)
Regards,
Answers
-
Hi,
It would be great if SQL Developer supported a convenient way to share user defined reports with other people on your team.
Then it is great, because that feature already exists. π
Ever noticed these?
But first, you must convert your reports into individual XML extensions. That's easy, and well explained in the following documents:
- https://github.com/PhilippSalvisberg/sqldev/blob/main/workshop/010_create_report_xml_extension/README.md#create-report-as-xml-extension
- https://github.com/oracle-samples/oracle-db-examples/tree/main/sqldeveloper/extension/xml/individual#sql-developer-examples
Don't forget to nest the main
<display>
element of your reports inside a<folder>
element in order to group them into folders under Shared Reports. (See the example in the end of this post.)Once you have done that, nothing prevents you from loading individual XML extensions from your local Git repository, making it possible to synchronize with your project's remote Git repository by just pulling from that remote, then restarting SQL Developer.
(It takes a bit of manual configuration work: each individual XML extension must be configured in Preferences. But once this is done, it just works. Restarting SQL Developer is required for changes to become available, though.)
Regards,
-
π
That's neat, not exactly obvious in the settings to find, but nice to know it's there!
Thanks,