How to implement Grouping of rows and adding back to pivot in DV

SiddharthDang-Oracle

Summary:

I have a requirement where we have 2 attributes that need to be added based on logic and added as a third row in the visualization. Any idea if that is possible in DV without dataflow?

Content (required):

Version (include the version you are using, if applicable):

Code Snippet (add any code snippets that support your topic, if applicable):

Gianni Ceresa

Sure, add a calculation.

It is only inside the workbook and doesn't need a dataflow, and let you do a bunch of things, including pointless things like this example of a sum of 2 numbers coming from some attributes.

SiddharthDang-Oracle

Hi Gianni,

Thanks for the response. However i am looking for grouping rows of data and creating an extra row. Like i have two rows of transactional data, one for attribute A and one for Attribute B. I want to show a third row of Attribute C which is a sum of A and B.

so my data has only two rows. Output should be three rows in a pivot table. This was easy in classic reporting. But could not find a way to do it in DV.

Michal Zima

I think, that what you are looking for, are features called Calculated Items and Groups (https://docs.oracle.com/en/middleware/bi/analytics-server/user-oas/manipulate-members-groups-and-calculated-items.html) - which are available in "Classics" (you can define them in Answers). We (as customer) are missing similar feature in DV, so I have created following Idea: https://community.oracle.com/customerconnect/discussion/631392/make-calculated-items-groups-features-available-in-dv - so if you matches your needs, give it a vote, pls.

Gianni Ceresa

Another proof that DV is not a replacement for "Classics" and it's time to stop forcing using DV just because it's the only piece being developed (trying to catch up with 15+ years of "Classics" doing the job perfectly).

Michal Zima

@Gianni Ceresa I agree - if Product Management has strategy to "move" customers from "Classics" to DV, than part of this strategy must be plan to bring (in reasonable timeframe) features, which has been build in "Classics" (for 15+ years) also in DV. Unfortunately this is happening very slowly, since main focus is on bringing into DV "augmented analytics" features (because Gartner likes it and will appreciate it in their magic quadrants), which is nice, but you have to first build solid "construction foundations" and then on top of those to put "first and second floor" (simple analogy from construction industry).

Gianni Ceresa

First build solid foundations before to add extra floors on top? 100%!

But I don't know why when I see DV I can't stop thinking at this...

SiddharthDang-Oracle

Hi @Michal Zima,

I have upvoted your idea. I also have the same view. When we are presenting to customers they get confused with two different GUIs for analytics. I feel the strong foundation of classic should be brought to DV first.

Regards,

Siddharth Dang

Amrita Gupta-Oracle

It seems Product development does not plan to bring all features from Classic into DV. I had recently enquired about the possibility of making set operations available in DV. But it does not seem to be on the road map. And it proves to be a challenge to explain this to the customers.

Gianni Ceresa

It becomes a challenge when everything starts by pushing DV for everything. It has no chance to catch up with everything classic does and it can't be the plan because it would take years. And when the "new features" are reproducing something that existed and worked for 15+ years inside the same tool, it's challenging to sell the product...