Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Export data options in OAS 2025 DV
Hello,
Trying to better understand what export options are available when viewing data visualizations in a workbook in OAS 2025. In Classic BI, for analyses, dashboards, etc, we have the option to export to excel, csv, pdf, etc, but not seeing any similar options anywhere in the modernized tools.
- Is it possible this feature in Oracle Analytics Cloud and not Oracle Analytics Server? That is the sense that I'm getting based on what I've gleaned thus far.
- Are there special permissions that need to be applied to a role via the grantPermissionSetsToBIRole script to enable export functionality? If so, what are they? I've gone over the list (https://docs.oracle.com/en/middleware/bi/analytics-server/security-oas/grant-or-revoke-permissions-assignments.html) and nothing there jumps out at me.
The only thing we see, when going into a visualization after entering edit mode, is to the right click. There is an option there that says "Export" and the only option under that is "File". When that dialog box comes, up there are no options to select what type of format you want your export to be in (Excel, PDF, etc). Screenshot below.
Other screenshots I see for this have more options.
Thanks in advance,
Chad
Best Answer
-
Hi Chad,
There are some "fine-grain" permissions
About PermissionsExport Workbook Data
Export Workbooks to Documents
These should be defaulted to DVConsumer roles, unless they specifically removed.
To Export a table or pivot table visualization in OAS 2025 requires some additional configuration.
Enable Users to Export to Excel
The export icon is just to the right of the light bulb.
Same as right-click > export
Additionally, Content Authors can enable and disable some options for Preview/Present mode.1
Answers
-
Are you looking for below information ?
Export a Visualization
You can specify the following output options when you export a visualization:
For Powerpoint (pptx), Acrobat (pdf), and Image (png) — Specify the file name, paper size, and orientation. When you share any of these visual formats, the visualization is re-rendered based on the size and orientation you select. So if you're sharing a table, then your output file might not contain all of the table's rows and columns displayed in your visualization. For Data (csv) — Specify the output file name. This option only includes the data used in the workbook. The output file uses the data delimiter for your computer's locale. For example, if your locale is set to Brazil, then the delimiter for numeric decimals is a comma instead of a period, which is used when your locale is set to United States. For Excel (xlsx) — Specify the file name for tables and pivots. For Package (dva) — Specify whether to include workbook data, connection credentials, and access permissions. To enable users to open the workbook DVA file without having to enter a password, click Include Connection Credentials and specify the password.
Regards,
Arjun
1 -
@SteveF-Oracle Your comment :
To Export a table or pivot table visualization in OAS 2025 requires some additional configuration
made me laugh. Good joke, really. Installing (manually not as a part of overall OAS 2025 binary installation) additional sw components (where installation requires direct internet connection from machine, where you are installing) , creating your own scripts for starting/stopping those sw components (again not part of overall start/stop script for OAS instance) is not a "piece of cake", especially in extremely secured environment like ours. And not to forget solving bug (hard coded port of managed server) connected with this functionality. So, pls, be honest and don't paint reality in rosy tones. I am still expecting that all components of this Export to Excel functionality will be (in next OAS release) included into standard OAS installation binaries (with really tiny manual adjustment/modification by customer), not DYI approach as it is now.
2 -
I would join Michal side on this…
@Chad Williams , if you can … don't tell your customer about the Excel export of tables and pivots visualizations in DV, because that one can quickly become more issues than benefits. As Michal hinted, the Excel export requires to run a different piece of code that expects your OAS to just be running with the basic default settings. After more than a year they just support a not-default port for the HTTP port (don't expect HTTPS) with the July patch.
By my understanding, a number of DV exports in OAC are handled by separate microservices. Obviously that become an issue with OAS, because it isn't designed as a Kubernetes or other containerised deployment. Therefore there can be less options in OAS for that. One of those microservice-based export has been provided with OAS 2024, it's the Excel export of table and pivot. But it stopped there… It was basic, not compatible with all the deployments and requiring you to keep a number of default settings to work (and you had manage it fully yourself, making sure the process is up and running etc.). Nothing really changed in OAS 2025 from that point of view (till the July patch to accept that not every environment does use HTTP port 9502).
2 -
Thanks for this Arjun! Yes, this is what we want to do, but for some reason, after clicking on Export → File, even for a simple table, there are no format options in the dialog box. This is unusual, right?
Regards,
Chad
0 -
Thanks, as always, @Gianni Ceresa for your helpful insight. I don't see us rolling out the data visualization piece of OAS to our wider user base, so we're good there. This is mostly for a small group of analysts who want to do Tableau/PBI style analysis. We'll probably just give access on a case by case basis. Most of our userbase is very much married to our Classic implementation, and would be a huge lift to move them away from that. DV is definitely not the direction there if we ever do try to replace it.
0 -
I think this is part or the whole of the problem. When we import Snapshot data from older instances of OBIEE or OAS, several of the pre-defined application roles are getting overwritten and replaced by what's in prior installations/versions of OAS. It's entirely possible we had to create the DV roles manually, and just never added fine grain permissions to those roles. And now, we've dragged that security security structure from older OBIEE versions, with perhaps a few added role and other debris into our newer environment.
My feeling is that I would very much like us to migrate over to start using the newer applications roles that are delivered out of the box with the OAS install. Especially the case if we are to consider putting our server instance in the cloud someday. Sorry, this is a separate question, but I assume that would be a fair amount of work, no?
Right now, when I look at DV Consumer and check the permissions tab, then only item in that page is the following:
Nothing else is added. I'll start trying to add a few things, and see where it gets us, but hopefully the documentation has all of the standard permissions documented for each role.
Regards,
Chad
0 -
@Michal Zima -
I just spent some time updating all my NodeJS, NPM packages/chrome libraries on Linux 9, didn't take long, but clearly a separate task outside of patching that takes time.
Ideally, I would like to see it packaged as an application and deployed like any other java app in Weblogic and patched like the product with opatch, but I think there are already Idea Lab requests for that and I have voiced my opinion to the relevant parties.
Not here to debate any of your valid points, I'm just the messenger ;-)1 -
@SteveF-Oracle Hi Steve, If you are (and I guess this is your case) on environment/machine without any security restriction (in terms of connectivity to Inet - since all NodeJs modules along with Chrome for Dev/Chromium installation are done from "public" Inet resources) then it is not that complicated. But we are central bank with strict security restirction and this is where "fun begins"….
I understand, that you are "just messenger", but I consider as a fair approach from Oracle to notify customers, interested about this "Export to Excel in DV" functionality in OAS about its caveats (to make it "up and runnung") and also about the fact, that integration of this functionality into to overall OAS product is very poor.
I have created Idea on this topic some time ago (https://community.oracle.com/products/oracleanalytics/discussion/21460/oas-2024-better-and-more-seamless-integration-of-export-to-excel-in-dv-functionality-into-oas), it is "Under Review" status and my goal is to bring as much attention as possible to all involved parties (obviously) and make pressure on implementation.
Michal
0 -
Post close - Oracle will review the comments.
1
