Skip to main content

Slicers vs. Dashboard Filters

Updated

Background information

This article explains the two primary data filtering mechanisms in MSPbots.ai: Slicers and Dashboard Filters. Understanding the distinct functionalities, configurations, and strategic applications of the platform is crucial for practical data analysis, dashboard design, and report creation.

Required permissions

  • Only admins can create slicers and dashboard filters.
  • MSPbots.ai users can use Dashboard Filters and Slicers to filter data in the dashboard.

1. Overview: Slicers and Dashboard Filters

MSPbots.ai provides robust tools to filter and analyze your business intelligence data. The two primary methods are:

  • Slicers: Interactive, user-driven controls on a dashboard that allow users to filter data in real-time dynamically.
  • Dashboard Filters: Administrator-configured, static filters applied at the dashboard level to establish a baseline data view for all widgets.

While both refine data, they operate differently and are suited for distinct scenarios.

2. Deep Dive: Slicers

Slicers empower end-users with direct control over the data they see, fostering interactive analysis.

dashboard with slicer

2.1. Core Functionality & User Interaction

  • Visual Controls: Appear as dropdowns, date pickers, input fields, and other elements directly on the dashboard.
  • Real-time Filtering: When a user makes a selection in a Slicer, linked widgets instantly update to reflect the chosen criteria.
  • Self-Service BI: Enables users to independently explore data ("slice and dice") without needing pre-defined reports for every query, accelerating insight generation.

2.2. Creation, Types, and Configuration

Creation

Slicers are created as independent, reusable components via Settings > Slicer. Refer to How to Create a Slicer in Widgets.

Slicer settings

Types, and Configuration

Name Description
Types of Slicers
  • Dropdown List: For selecting from predefined categorical values.
  • Date Range: For specifying periods.
  • Input: For free-text search.
  • Cascader List: For hierarchical selections.
Key Configuration Fields Name, Description, Role( Basic identification and access control).
Data Source The dataset that populates the Slicer's options (e.g., a list of companies). Must align with widget datasets.
Text The user-visible label for an option (e.g., "John Doe").
Value The actual data value used for filtering (e.g., "EmployeeID123"). Separating Text and Value enhances user experience and data integrity.
Default Value Initial state on dashboard load (e.g., 'ALL' or 'Only First').
QueryParams A critical linking mechanism. This value (e.g., "companyFilter") must match a parameter in the filter settings of the target widgets.
Placeholder/Watermark Hint text within the Slicer (e.g., "Select Company").
Multiple Mode Allows selection of multiple Slicer options if checked.
Strict Mode
  • If enabled, widgets display nothing when all Slicer options are cleared.
  • If disabled (default), widgets display all data.

 

2.3. Integration with Dashboards and Widgets

  • Adding to Dashboard: Go to Dashboard Design Mode > Add Widget > Slicer List. Refer to How to Add a Slicer to the Dashboard.
  • Linking to Widgets: Adding a Slicer to a dashboard isn't enough. Each widget to be controlled by the Slicer must be explicitly configured. Refer to How to Add a Slicer to the Dashboard. 
    1. Edit the target widget.
    2. Go to its filter settings.
    3. Add a new filter condition, select the relevant data column, choose the IN operator.
    4. Enable the "Slicer" checkbox and input/select the Slicer's QueryParams value.
  • "Ignore Filter" Option: When linking a Slicer to a widget, if "Ignore Filter" is checked for a field, the Slicer's input for that field overrides any pre-existing static filters defined directly within the widget for the same data field.

2.4. Slicers in Scheduled Reporting

For detailed information, refer to How to Set Up Scheduled Reporting for Dashboards and Reports.

  • "Save Slicer" Option: When scheduling a report for a dashboard with Slicers:
    • If ON: Recipients can interact with the Slicer in the received report to change views. The report initially shows data based on the Slicer value at the time of scheduling.
    • If OFF: The Slicer is static in the report; recipients see data based on the Slicer value set during scheduling but cannot change it.

      save slicer.jpg

  • Company Slicers (QueryParams="Company"): Often exhibit special behavior for automated, company-specific report distribution, particularly with the "Automated Contact List," streamlining multi-tenant reporting for Managed Service Providers (MSPs).

    Contact List.jpg

3. Deep Dive: Dashboard Filters

Dashboard Filters establish a foundational, administrator-defined data context for an entire dashboard.

3.1. Core Functionality & Application

  • Admin-Configured: Set by administrators to apply a baseline filter to all widgets on a dashboard (e.g., limit data to a specific date range, region, or status by default).
  • Consistent Starting Point: Ensures all users begin with a standardized view before any Slicer interaction.

3.2. Creation and Configuration

Dashboard Filters are created directly within a specific dashboard's settings (usually via a filter icon > "Add A Filter").

dashboard filter_2 (1).jpg

  • For the Configuration Steps, refer to the following articles:
  • Condition: Define filter criteria (e.g., Status = 'Open' AND Priority = 'High') based on fields from datasets used by widgets on that dashboard.
  • Filter Switch: A global on/off toggle for the entire Dashboard Filter.
  • Dataset Dependency: Dashboard Filters can only be based on datasets already used by widgets on that dashboard.

3.3. Impact on Widgets and User Toggling

  • Automatic Application: Active Dashboard Filters automatically filter relevant widgets, which usually display an icon indicating an active filter.
  • User Toggling (Per Widget):Any user can typically disable/enable a Dashboard Filter's effect on a specific widget by clicking the filter icon on that widget.
    • If the user has edit permissions for the dashboard, this toggle change is saved for all users.

      Filter.gif

    • If the user lacks edit permissions, the toggle is temporary for their session.

      Filter-1.gif

3.4. Relationship with Slicers (CRITICAL DISTINCTION)

  • Slicer Options are NOT Filtered: The most essential concept to grasp is that Dashboard Filters DO NOT filter or reduce the list of options available within a Slicer control.
  • Independent Data Sources: Slicers populate their options from their own defined datasets, independent of any active Dashboard Filters on the dashboard.
  • Example: A Dashboard Filter might set widgets to show "Company A" data. A "Company" Slicer on the same dashboard will still list "Company A, Company B, Company C," etc., because its list comes from its data source. If a user then selects "Company B" in the Slicer, the widget (if linked) will respond to the Slicer.

4. Slicers vs. Dashboard Filters: Key Functional Differences

 
Feature Slicers Dashboard Filters
Primary Purpose Interactive, user-driven filtering. Admin-defined, foundational filtering for a dashboard.
User Interface Visual, on-dashboard controls (dropdown, date picker). Backend configuration; users may toggle the effect per widget.
Creation Method Separate entity (Settings > Slicer); added as a widget. Directly within a specific dashboard's settings.
Scope of Application Applied to individual widgets explicitly linked to it. Applied to all widgets on the dashboard using the specified dataset(s).
User Control High: Users directly change filter criteria. Low: Users typically only toggle effect, not change criteria.
Slicer Data Options N/A (Defines its own options) Does NOT filter the data options available within Slicers.
Reusability High: Created once, usable on multiple dashboards/reports. Low: Defined for and tied to a specific dashboard.
Scheduled Reports Can be interactive for recipients if "Save Slicer" is ON. Applied statically based on dashboard configuration at time of generation.
 

5. Strategic Application: When to Use Which

5.1. When to Use Slicers

  • Interactive Data Exploration: Users need to dynamically change filters to investigate data.
  • Personalized Views: Different users need to tailor data on a shared dashboard to their specific needs.
  • "What-If" Analysis: Rapidly seeing the impact of different parameter selections.
  • Filtering Across Diverse Widgets: A single Slicer selection updates multiple charts, tables, and KPIs.
  • Empowering Non-Technical Users: Providing intuitive controls for self-service data analysis.
    • Ideal for: Dashboards for active analysis, operational management, and agile decision support.

5.2. When to Use Dashboard Filters

  • Establishing Foundational Context: Setting a default, consistent scope for an entire dashboard (e.g., current fiscal year).
  • Pre-filtering for Specific Audiences: Defaulting a dashboard view for a particular group (e.g., regional sales data for a regional manager).
  • Applying Broad, Static Criteria: For stable business rules or reporting requirements not needing user modification.
  • Simplifying User Experience: Presenting a less overwhelming initial data view.
    • Ideal for: Enforcing data governance, standardizing perspectives, ensuring consistency in reporting.

5.3. Using Slicers and Dashboard Filters in Tandem

This creates a layered filtering experience:

  1. Dashboard Filter sets the broad, foundational context (e.g., "Current Fiscal Year").
  2. Slicers allow detailed, interactive exploration within that context (e.g., filter by "Quarter," "Salesperson," "Client" within the current fiscal year data).
Always remember the independence of Slicer data options from Dashboard Filters. The Slicer will always present its full range of options from its own data source, regardless of the Dashboard Filter settings.

6. Conclusion and Recommendations

  • Prioritize Slicers for dynamic analysis, self-service BI, and scenarios requiring frequent user-driven filter changes.
  • Opt for Dashboard Filters for consistent, predefined views, or to enforce standard reporting scopes.
  • Use in Tandem Strategically: Combine Dashboard Filters for a stable baseline with Slicers for flexible exploration. Plan their interaction carefully to avoid user confusion, clearly understanding that Dashboard Filters do not narrow down the choices within Slicer controls.
  • Test: Experiment with both tools in MSPbots app to fully grasp their behavior and optimize configurations for your specific BI objectives.