Thanks @Avinash Krishnaram-Oracle ! Can I also make a suggestion that we can make Export to Excel its own link in the menu to save on clicks? Most of our users either just take a screenshot/snippet of the graph or dashboard they use or Export to Excel. Most of the other Export options are rarely ever used.

I have been using the "Preview" of this feature and it's less than desirable. It can only be used when you have the whole workbook open. If you have a canvas embedded on an Answers dashboard page, the export option does not appear. Secondly, when you do get the Excel export option to appear, you can only use it if you have…

I love both options here.

I have two suggestions to add to this. * We should be able to create folders to organize the columns. * We should have a quick button that chooses the sort the columns alphabetically ascending or descending

I agree that this technically exists but the formatting of the data is less than desirable. We have to take this data and put it through a data flow and create a bunch of new columns just so we can make it useful. Oracle needs to create a native usage tracking dashboard for all customers who have OAC.

I understand how adding an attribute to a tool tip can cause grain of detail issues; however, if we're aware of that limitation, we can make it work. Not every field in the view needs to be in full display on the report. With the ability to "hide" fields in a tool tip, the user has the ability to hover over the data point…

I have had pretty much zero success using Extensions/Plugins in DV. I told my team to stop using them because they are unreliable and very buggy. If Oracle plans to add presentation variables in DV, it will need to be built in functionality or it will be destined to fail, in my opinion.

As an alternative to this, there are two other enhancements that would make this better. * You should build in single cell "keep selected" so you can put that one value up in the filters banner with a quick click. Also if that field is already in the banner, it should just update that one filter instead of adding a new…

I also have scenarios where I have an "ID" field that I need in the table for Data Actions but they don't need to be displayed in the view. In OBIEE, I would just add the column to the table and just hide it. I know this functionality exists because if you convert an OBIEE report to DV, it will do it but it can't be done…

This would dramatically help since the data blending is so limited

Each DV workbook needs to be able to join datasets independently of another. This is causing major issues on my team where we create one dataset that should be able to be used for multiple purposes. If someone creates a workbook with joins, they think their work is done. Then someone comes in and creates another workbook…

This is the number 1 complaint about OAC DV from my users. It's brought up daily.

Agreed that this is a pain point. My best solution is to "Revert to Saved" but then you leave whatever canvas you were on and go back to the default one. In OBIEE, I trained my users to use the the "Clear my customization" option. Something like this would be great.

I won't name any names but my Oracle reps have told me that they are not going to make any enhancements to Classic dashboards anymore and they are going to focus only on DV enhancements.

This is probably not an approved solution by Oracle since they are trying to get rid of OBIEE (Classic) dashboards but I have gone with a hybrid approach. I create my DV report and put each canvas as a page on a classic dashboard. I then create a classic dashboard prompt using the same dataset and also put that on the…

I agree that this is a must have feature. The only way around this is to rebuild the dataset from scratch against the different databases. We need to be able to develop in DEV against a non-prod database then promote that dataset to production and swap out the connection to use the prod database. Otherwise, Oracle is…

This would be an ideal metric to track. Other tools provide this solution.

Why did you take this functionality away?

I love this idea. I never thought about this but it would be really powerful

Why did Oracle create a "better" tool and take away functionality in the process?