Multiple Cubes - One Filter

Follow

Sam Hughes

October 23, 2019 14:55

I'm building a customer health dashboard that combines top=level metrics from multiple cubes. I would like a way to have 1 text/name filter to select the customer's name but the data comes from multiple cubes.

Is there a way to combine filters to cover the same field (customer name) when it's listed in multiple separate cubes.

I know this is an odd & specific request - but it's a pain in the butt so I thought I would try.

0

• 

  Nathan Giusti November 13, 2019 15:36

  Not that I am aware of. It would be better (and more in line with Sisense best practice) to just load all the data into a single elasticube. 

  0

  Comment actions Permalink
• 

  Ravid Paldi November 14, 2019 11:39

  Hi Sam, 

   

  As Nathan said rightfully, the best practice would be to merge those several cubes into one cube (you can use the other cubes as a data source like any other data-source for that purpose). 

  If it is not possible in your case, you can develop a custom plugin that will listen to filter changes and each time it happens - duplicate that filter selection to all the data sources that are run within the dashboard. 

  I your having troubles developing it feel free to reach out with some questions, we're always happy to help. 

  We can also provide you with a price quote for a finalized plugin. 

  Good luck (:

  Ravid

  ravid@paldi.solutions

  Paldi Solutions

   

   

   

   

   

  0

  Comment actions Permalink
• 

  Tamir Basin November 15, 2019 05:12

  Hello,

  If you use the exact same names for the table and column ( for the customer name) then using it from one of the ECs should work fine for all the rest.

  It makes sense to use it for example when using a dim table that is used across all ECs.

  0

  Comment actions Permalink
• 

  Ravid Paldi February 04, 2020 10:47

  Hi Everyone, 

   

  We're working with one of our clients on implementing a similar behavior with few additional customization so I have some info to share: 

  1) Feel free to read about it in this case study that Sisense had published recently, search for the MyTeam plugin within the post

  2) Tamir Basin. From our experience, your suggestion won't work  it is not enough to use the same names as filters definition includes their destination DataSource so you one filter would filter out only one DS even if they have the same name.

  3) In general relaying on specific names is risky approach. I would recommend only as the absolute last resort because Sisense has a very limited "deep renaming" functionality (there is none to be more accurate). 

   

  I hope it helped.

  Cheers,

  Ravid

  0

  Comment actions Permalink

Please sign in to leave a comment.