Oracle Communities

Oracle Analytics and AI

Child Item

Hierarchy building capability in data visualization to avoid additional work in data modeler or RPD

Organization Name

xerox corporation

Description

We need hierarchy building capability on data set directly in data visualization data plane. This feature is already exist in tableau, power bi etc analytics tool and it helps to build hierarchies on the fly. To build hierarchies we need to work on data modeler but we found a bug that detailed column in hierarchy is avoiding distinct in physical queries and causing duplicate rows. So we need to use RPD to achieve hierarchy and to avoid duplicates.

Use Case and Business Need

Business users can directly build hierarchies on relevant fields with out IT people help.

More details

We thought of building hierarchy reports without using RPD but due to lack of this capability we have to chose either thin client or RPD. For some reports data modeler is enough but choosing either RPD or data modeler is restricting to build some important reports.

Original Idea Number: c8944097a2

Find more posts tagged with

Under Review

Reporting

Analysis and Data Visualization

Status: Under Review

Comments

Michal Zima

One addition to this requirement - capability of building/designing hierachies should be available in data set definition. And this hierarchy should be exposed (in DV projects visualization) in similar way as hierarchical columns in Answers.

Subhakara Netala-Oracle

Hierarchy building capability in DV Dataset is very useful. Customers are asking for this functionality. Is there any update on this from Product Development Team?

Aaron Epstein-261578

This would be incredibly helpful for some reporting that we're trying to stand up here too that doesn't exist in our RPD model.

Greg Faris

We really need this feature to build hierarchical dimensions with defined drill-paths in dataset-based DV reports similar to what can be accomplished with different levels in logical dimensions in an RPD. It's a gap of functionality that exists in many other BI tools as mentioned above. It is preventing us from being able to migrate reports from other platforms into OAS.

Can someone from Oracle please provide an update on when this feature is planned for implementation?

Note that the initial Idea is 3 years old, so it would be good to know that it's on the roadmap in the near future at this point.

Rajakumar Burra

Yes. It will help lot.

Qlik has this capability.

Benjamin Arnulf-Oracle

I agree. It would be extremely helpful. We need more votes on this idea. Adding my vote.

user6766570

I agree. It would be extremely helpful. We need more votes on this idea. Adding my vote.

User_FBG8L

It was this the lack of this feature & another one that prevented our client months ago from taking OACs over Power BI. Their users could not contemplate having to go through an RPD to build something they thought was super simple. Please add this as it make reports much easier to consume.

Junaid Zahid

The Hierarchy building capability directly in Oracle Data Visualization (DV) would be a great enhancement — it would help avoid additional work in the Data Modeler or RPD.

In large enterprise environments using big datasets and Oracle ERP, we often need to create flexible dashboards in DV without depending on RPD-based hierarchies. Currently, when I try to create new DV dashboards in OAS 7.0 using PL/SQL query-based datasets, I face issues because hierarchy levels and session variables are tied to the RPD (Admin Tool).

Our business requirement is to have hierarchy- and level-based dashboards that dynamically change according to the logged-in user. For example, when User A logs in, the dashboard filters data according to A’s hierarchy level, and when User B logs in, it adjusts automatically for B’s access level.

It would be extremely helpful if OAS DV could support user-based session variables and hierarchy definitions natively, without needing to go back to the RPD. This would make DV far more agile for modern self-service and role-based analytics use cases.

Is there any planned update or workaround to achieve this within OAS 7. 0 DV directly?

User_FBG8L

We have to build Semantic Models just to use hierarchies. This is silly as most of our use cases should not require building semantic model as it comes with added overhead & maintenance. It begs the question as to why we are building data models in different places; I understand they serve different purposes but semantic model really should be combined with the data modelling in DV so there is only a single place to build models.