Dynamically generate Levels in Parent-Child Hierarchy - Hierarchical Slicer

[abhiram342]

Hi Team,

I have Pipelines table below with Child and Parent PipelineId, We want to generate Hierarchy Slicer based out of it. Currenlty, I was able to generate manually using Path and PathItems  with sample data, however, we have  ParentPipleineIds  in the  range from 2 to 16  for some PipelineTypes, I believe generating 16 Columns will degrade the perfome of model . Is there any alternative Solution  Or Cloning the Table with relationships/ Redesign? Please Suggest

Pipeline Table RowCount is 5 Million rows

Also, Regaridng Blank Value For Each Parent, Can we achieve same behaviour by clicking on Parent and Elimintaing Blank Value?

( Highlighted) 

Thanks,

Abhiram

[lbendlin]

Hypothetically, if you had that hierarchy - what do you think will be the maximum number of clicks before your users abandon you?

What are you ultimately trying to achieve?

[abhiram342]

Hi @lbendlin - thank you for your reply! I wrongly calculated the level. Currenlty, max depth level is 16. Also, this number may increase in future. Looking for solution on how to the cretae Levels dynamically if the depth increases? As, we want to include the Levels dynamically in hierarchical slicer i.e currently we have level 16 and if new level comes we need to manually create column for new level and also bring the column in hieraricahl slicer.

Please find scenario below

we want to create dashboard to track the Pipelines , Activities and Tickets for product. User is intersted in hierarchical slicer to understand the dependecies of pipelines and how they execute.

Pipelines: Pipelines Tables will have list of Parent and Child Pipelines information , attributes inlcudes, PipelineId, ParentPipelineId, created date, start date, finish date, owner, pipelinetype, product . All the Pipelines with be group based on Product. ex: Product A has 10 pipeleines ( 5 parent pipeline and each parent has child pipeline)

Activities: Each Pipeline will have activities to do some action and attribute includes ( PipelineId, ActivityId, PipelineName, StartDate, EndDate, Type, Owner, Order).

Tickets: Each Activity will create ticket if there are any failures, same Activity (ActivityId) can create multiple tickets. ActivityId, TicketId, TicketCount.

3 Tables - Pipelines, Activites, Tickets.

Thanks,

Abhiram

[lbendlin]

we want to create dashboard to track the Pipelines , Activities and Tickets for product. User is intersted in hierarchical slicer to understand the dependecies of pipelines and how they execute.

That's pretty much a non-starter as dashboards are not interactive unless you pin an entire report page to a tile.