Filter drill down fields per widget

Follow

Eli

February 23, 2015 10:38

Download: Filter Drill Down

Introduction

We will introduce how to filter, drill down fields on widget basis.

 

Steps:

Step 1:

Download the attached plugin and place in .../PrismWeb/plugins, if plugins folder does not exist please create it. If you are using version 7.2 and higher unzip the contents into your C:\Program Files\Sisense\app\plugins\ folder. 

Step 2:

Go to the widget script of the widget you want to apply the filtering on and add the following script, describing which fields you want to remove or keep:

var fieldsToKeep = ['[Annual Performance.OrderYear]', '[Orders.CustomerID]', '[Products.ProductName]'];
var fieldsToRemove = [];
prism.FilterDrillDownFieldsPerWidget(widget, fieldsToKeep, fieldsToRemove);

 

step 3:

refresh the page

 

Example:

 

 

To apply it on dashboard basis you can have a look at this: https://support.sisense.com/entries/52397100-Filter-drill-down-fields

 

To remove the drill history for good (it will never appear) we can use dashboard script:

dashboard.on('domready', function(d,e){
_.each(d.widgets.$$widgets, function(widget){
        if(widget.metadata.drillHistory != undefined){
            delete widget.metadata.drillHistory;
        }
    })
})

 

 

Good Luck!

The plugin was updated to work on version 6.5

0

• 

  shilpa March 03, 2015 19:00

  Tried this . Got the Plug-in but did not work. 

  //Script to disable "Drill-into" functionality on a specific widget
  //This will work only if there is no script related to Drill-into at the Dashboard level
  prism.disableDrillDown(widget);
  
  */
  var fieldsToKeep = [];
  var fieldsToRemove = ['[Revenue_Detail.ProjectNumber]'];
  prism.FilterDrillDownFieldsPerWidget(widget, fieldsToKeep, fieldsToRemove);

  I have 8 tables in the elasticube. How do I not show 7 tables and display certain columns in one table?

   

   

  0

  Comment actions Permalink
• 

  Tony Fonager March 06, 2018 16:13

  Seems like this is not in 6.7.1.15016

  Any updated versions of the script ?

  0

  Comment actions Permalink
• 

  support cessoftware March 21, 2018 12:03

  This plugin does not work with version 7.0.2.11001, when trying to use the field selector during editing of widgets, the field selector box does not populate.

  0

  Comment actions Permalink
• 

  Graeme Davidson May 22, 2018 08:13

  Hi, I can't get it to work, but I may be doing something wrong.  Also, I don't want to permanently remove the filters.  just remove them now, so that the next time they use them it will be the correct filters.

   

  

  0

  Comment actions Permalink
• 

  Samuel Mendu March 19, 2019 18:42 (Edited March 19, 2019 19:01)

  Plug In is not working for date-time fields

  0

  Comment actions Permalink
• 

  Chris Kerrison November 01, 2019 16:48 (Edited November 01, 2019 16:49)

  As suggested in the post, I want to apply this from the dashboard level so it is automatically applied to all widgets. The link in the post does not work though. this is what I've got in my dashboard script but it's not working 

  _.each(prism.activeDashboard.widgets.$$widgets, function(widget){
  var fieldsToRemove = ['[timesheet details.Revenue]', '[timesheet details.Net Savings]'];
  var fieldsToKeep = [];

  prism.FilterDrillDownFieldsPerWidget(widget, fieldsToKeep, fieldsToRemove);
  });

  It works fine on an individual widget though but some dashboards have  8 widgets on them

  0

  Comment actions Permalink
• 

  Chris Kerrison February 20, 2020 18:40

  It doesn't look like this plugin works with version 8.1.

  When you click on the drill into option, the field list popup box doesn't show anything at all. And, in the developer console window there is an error -

  common.js?g=4874335bfec11091b9ca5e1b9ec6de10:13 TypeError: promise.success is not a function
  at Object.getFields (main.9928a6b34e00da468ce0.js:1)
  at R (app-account.js?g=4874335bfec11091b9ca5e1b9ec6de10:357)
  at t.e.loadMore (app-account.js?g=4874335bfec11091b9ca5e1b9ec6de10:357)
  at Object.<anonymous> (app-account.js?g=4874335bfec11091b9ca5e1b9ec6de10:357)
  at Object.invoke (common.js?g=4874335bfec11091b9ca5e1b9ec6de10:13)
  at _.instance (common.js?g=4874335bfec11091b9ca5e1b9ec6de10:13)
  at se (common.js?g=4874335bfec11091b9ca5e1b9ec6de10:13)
  at common.js?g=4874335bfec11091b9ca5e1b9ec6de10:13
  at common.js?g=4874335bfec11091b9ca5e1b9ec6de10:13
  at app-account.js?g=4874335bfec11091b9ca5e1b9ec6de10:357 "Possibly unhandled rejection: {}"

  I believe the "Possibly unhandled rejection: {}" is an Angular error. 

   

   

  0

  Comment actions Permalink

Please sign in to leave a comment.