Get Free Trial
  1. API reference
  2. Welcome
    1. Introduction
    2. Get Flexmonster
    3. Quick start
    4. System requirements
    5. Troubleshooting
    6. Managing license keys
    7. Migrating from WebDataRocks to Flexmonster
  3. Integration with frameworks
    1. Available tutorials
    2. Angular
      1. Integration with Angular
      2. Flexmonster usage in Angular
    3. React
      1. Integration with React
      2. Flexmonster usage in React
    4. Vue
      1. Integration with Vue 2
      2. Flexmonster usage in Vue 2
      3. Integration with Vue 3
      4. Flexmonster usage in Vue 3
    5. Other integrations
      1. Integration with Python
        1. Integration with Django
        2. Integration with Jupyter Notebook
      2. Integration with React Native
      3. Integration with Blazor
      4. Integration with AngularJS (v1.x)
      5. Integration with TypeScript
      6. Integration with R Shiny
      7. Integration with jQuery
      8. Integration with Ionic
      9. Integration with Electron.js
      10. Integration with Webpack
      11. Integration with RequireJS
  4. Connecting to Data Source
    1. Supported data sources
    2. JSON
      1. Connecting to JSON
      2. Connecting to JSON using Flexmonster Data Server
      3. Managing data presentation in JSON
    3. CSV
      1. Connecting to CSV
      2. Connecting to CSV using Flexmonster Data Server
      3. Managing data presentation in CSV
    4. Database
      1. Connecting to SQL databases
      2. Connecting to a MySQL database
      3. Connecting to a Microsoft SQL Server database
      4. Connecting to a PostgreSQL database
      5. Connecting to an Oracle database
    5. Flexmonster Data Server
      1. Introduction to Flexmonster Data Server
      2. Getting started with Flexmonster Data Server
      3. Flexmonster Admin Panel Guide
      4. Data sources guide
      5. Security and authorization guide
      6. The Data Server as a DLL
        1. Getting started with the Data Server as a DLL
        2. Referencing the Data Server as a DLL
        3. Implementing the API controller
        4. Implementing the server filter
        5. Implementing the custom parser
        6. DLL configurations reference
        7. The controller's methods for request handling
      7. The Data Server as a console application
        1. Installing the Data Server as a console application
        2. Configurations reference
        3. Data sources guide
        4. Security and authorization guide
      8. Troubleshooting the Data Server
    6. MongoDB
      1. Introduction to Flexmonster MongoDB Connector
      2. Getting started with the MongoDB Connector
      3. Embedding the MongoDB Connector into the server
      4. Configuring the MongoDB Connector
    7. Microsoft Analysis Services
      1. Connecting to Microsoft Analysis Services
      2. Getting started with Flexmonster Accelerator
      3. Referencing the Accelerator as a DLL
      4. Configuring the authentication process
      5. Configuring a secure HTTPS connection
      6. Troubleshooting
    8. Custom data source API
      1. Introduction to the custom data source API
      2. A quick overview of a sample Node.js server
      3. A quick overview of a sample .NET Core server
      4. Implement your own server
        1. Implementing the custom data source API server
        2. Implementing filters
        3. Supporting more aggregation functions
        4. Supporting multilevel hierarchies
        5. Returning data for the drill-through view
        6. Testing your custom data source API server
    9. Elasticsearch
      1. Connecting to Elasticsearch
      2. Configuring the mapping
    10. Connecting to other data sources
  5. Accessibility
    1. Accessibility overview
    2. Keyboard navigation
  6. Configuring the component
    1. Available tutorials
    2. Getting started with the report
    3. Configure the data source
      1. Data source
      2. Mapping
    4. Define which data to show
      1. Slice
      2. Custom sorting
      3. Calculated values
    5. Manage Flexmonster’s functionality
      1. Options
      2. Configuring global options
    6. Format fields
      1. Number formatting
      2. Date and time formatting
      3. Conditional formatting
  7. Saving component configs
    1. Available tutorials
    2. Save and restore the report
    3. Share the report
    4. Export and print
  8. Charts
    1. Available tutorials
    2. Flexmonster Pivot Charts
    3. Integration with Highcharts
    4. Integration with amCharts
    5. Integration with Google Charts
    6. Integration with FusionCharts
    7. Integration with any charting library
  9. Customizing
    1. Available tutorials
    2. Customizing the Toolbar
    3. Customizing appearance
    4. Customizing the context menu
    5. Customizing the grid
    6. Customizing the pivot charts
    7. Localizing the component
  10. Security
    1. Security in Flexmonster
    2. Security aspects of connecting to an OLAP cube
      1. Ways of connecting to an OLAP cube
      2. The data transfer process
      3. Data security
      4. Data access management
  11. Updating to the latest version
    1. Updating to the latest version
    2. Release notes
    3. Migration guide from 2.8 to 2.9
    4. Migration guide from 2.7 to 2.8
    5. Migration guide from 2.6 to 2.7
    6. Migration guide from 2.5 to 2.6
    7. Migration guide from 2.4 to 2.5
    8. Migration guide from 2.3 to 2.4
    9. Migration guide from 2.2 to 2.3
  12. Flexmonster CLI Reference
    1. Overview
    2. Troubleshooting the CLI
    3. flexmonster create
    4. flexmonster add
    5. flexmonster update
    6. flexmonster version
    7. flexmonster help
  13. Documentation for older versions
Table of contents

Implementing the server filter

The server filter can be used to limit which data is shown on the grid depending on a user’s role. It allows filtering the data right on the application’s back end, so Flexmonster Pivot receives and shows only the subset of the data that meets filtering conditions.

In this guide, we describe the concept of the server filter, its structure, and provide an example implementation:

The general idea of the server filter

The main advantage of the server filter is that it can be used as a data access management tool. Using the server filter, Flexmonster.DataServer.Core.dll will filter the data based on the user role received from Flexmonster Pivot.

Here is a possible server-side filtering implementation:

  1. When Flexmonster Pivot sends a request for data to the server, the user’s role can be included in the request headers with customizeAPIRequest. This method allows editing the headers before the request is sent to the server.
  2. After the Data Server accepts the request, the request headers can be read. Depending on the received role, the DLL can apply the appropriate filter to the data.
  3. The resulting subset of data is sent to Flexmonster Pivot. The component gets the dataset specific to the current user.

To see how the server filter can be implemented, refer to the Example section.

Example of a server filter

To simplify the server filter’s implementation, we designed a sample ASP.NET Core application using Flexmonster.DataServer.Core.dll. This application contains an example server filter, which can be viewed in the FlexmonsterAPIController.cs file.

To create a new ASP.NET Core application with the Data Server or to embed the DLL in an existing project, refer to the guide on Flexmonster.DataServer.Core.dll.

Defining user roles on the server side

In the sample, the data is filtered based on the user’s region token sent by the component using request headers. A dictionary defines which subset of data should correlate to the received token. The dictionary contains all possible region tokens and field members corresponding to them:

private static Dictionary<string, List<object>> _userPermissions =
new Dictionary<string, List<object>>()
/* a user with the "AdminToken" token will see
the report on all the countries */
{"AdminToken", null },

/* a user with the "EuropeToken" token will see
details about Germany and France */
{"EuropeToken", new List(){ "Germany","France" } },

/* a user with the "AmericaToken" token will see
highlights about USA and Canada */
{"AmericaToken", new List(){ "USA","Canada" } },

/* a user with the "AustraliaToken" token will see
info about Australia */
{"AustraliaToken", new List(){ "Australia" } },

Defining the server filter

In the sample project, the server filter is defined in a separate function. First, a user token is read from the request headers, and then the filter is applied:

private ServerFilter GetServerFilter()
// get the user token from the request headers
HttpContext.Request.Headers.TryGetValue("UserToken", out StringValues userRole);
if (userRole.Count == 1)
// create a server filter
ServerFilter serverFilter = new ServerFilter();
// specify a field to filter
serverFilter.Field = new Field() {
UniqueName = "Country",
Type = ColumnType.stringType
// include the members that correspond to the user token
serverFilter.Include = _userPermissions[userRole[0]];
return serverFilter;
return null;

To learn more about the server filter’s parameters and their types, see the server filter structure

Applying the server filter

After the filter is specified, it is passed as a parameter to GetMembers() and GetAggregatedData() methods, for example:

public MembersResponse PostMembers([FromBody]MembersRequest request)
var response = _apiService.GetMembers(request, GetServerFilter());
return new JsonResult(response);

To apply several server filters, add them to an IEnumerable<ServerFilter> collection and pass it to GetMembers() or GetAggregatedData() methods.

The server filter structure

The server filter has the following structure:

public class ServerFilter
public Field Field { get; set; }
public List<object> Include { get; set; }
public List<object> Exclude { get; set; }

Below is a detailed description of the filter parameters:

  • Field – Field. The field to filter. If a non-existent field is specified, Flexmonster.DataServer.Core.dll throws an exception.
  • Include – List<object>. Field members to include in the server’s response.
  • Exclude – List<object>. Field members to exclude from the server’s response.

Here is an example of how the server filter can be created:

ServerFilter serverFilter = new ServerFilter();
serverFilter.Field = new Field() {
UniqueName = "Country",
Type = ColumnType.stringType
serverFilter.Include = new List<object>(){ "USA", "Canada" };

What’s next?

You may be interested in the following articles: