Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture
Comments
-
@User_NP7ZZ One thing I noticed is that the employee and managers keys need to be numeric values. It will not work with text. For example: Employee number, Manager Number, Employee Name, Department, Job Title 1234, 5678, John Smith, Corporate, Analyst
-
I was able to successfully get the custom plugin to work but it has some pretty annoying flaws that makes it virtually unusable. It always resets back to the top of the org. My org has 5000 people in it and it's a lot to peg into. Filters do not work at all. I would like to be able to filter to a person or a department and…
-
My team and I have recently made a rule that we CANNOT use the import DVA feature AT ALL because it breaks way too many things in the process, such as permissions. Anxiously looking forward to improvement here. Current state, we have resorted to rebuilding everything from scratch because that is the only way we know it…
-
We need OAC and the RPD to be able to be harvested in Oracle's Data Catalog. Then we would be able to do documentation on all objects, whether they are tables, columns, RPD Subject areas, answers reports, DV reports. We would need to have information like: * who the owner is * who last modified * when it was created * when…
-
My company also uses O365. As much as I don't like people creating datasets out of excel, it doesn't look like it's going to stop. We have to use Python to work around this. Having a connector would make it so much simpler.
-
@Michal Zima Thanks for the quick reply. I definitely understand that it would be complicated when it comes to workbooks with multiple datasets in them. My assumption would be that if you create a calculation that uses two different subject areas, you would just get denied to save it. The part that you brought up about…
-
This is another feature that exists in OBIEE but Oracle decided not to include in OAC. What's super frustrating about this is it is actually capable of being done. If you have an Answers report with a hidden column and choose to "explore as workbook" the column will remain hidden. It even shows up as a greyed out field.…
-
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.