The data source is a required part of the report object. Flexmonster supports data from OLAP data sources, SQL databases, CSV and JSON static files, and inline JSON data. Each data source requires specific properties to be set inside the dataSource section of the report object. Read more in the following sections:

• Data from OLAP data sources
  • Microsoft Analysis Services
  • Mondrian
• Elasticsearch
• SQL databases
• CSV data sources
• JSON data sources
• Change the data source using the Toolbar
• Data source via API

Data from OLAP data sources

OLAP data sources include Microsoft Analysis Services and Mondrian. There are two ways to connect to an OLAP cube using Flexmonster Pivot:

1. via the XMLA protocol – an industry standard for data access in analytical systems
2. via Flexmonster Accelerator – a special server-side utility developed by Flexmonster

Microsoft Analysis Services

Here is a list of dataSource properties used to connect to Microsoft Analysis Services:

• catalog – String. The data source catalog name.
• cube – String. The given catalog’s cube’s name.
• dataSourceInfo (optional) – String. The service info.
• type – String. The type of data source. In this case, it is "microsoft analysis services".
• proxyUrl – String. The path to the proxy URL. Both tabular and multidimensional model types are supported.
• binary (optional) – Boolean. A flag to use Flexmonster Accelerator instead of the XMLA protocol.
• effectiveUserName (optional) – String. Use when an end-user identity must be impersonated on the server. Specify the account in a domain\user format.
• localeIdentifier (optional) – Number. The Microsoft locale ID value for your language.
• roles (optional) – String. A comma-delimited list of predefined roles to connect to a server or a database using the permissions defined by that role. If this property is omitted, all roles are used and the effective permissions are the combination of all roles. For example, to combine "admin" and "manager" roles, set the roles property like so: roles: "admin,manager".
• subquery (optional) – String. The parameter to set a server-side filter to decrease the size of the response from the OLAP cube. For example, to show reports for only one specific year set the subquery like so: "subquery": "select {[Delivery Date].[Calendar].[Calendar Year].&[2008]} on columns from [Adventure Works]".
• requestHeaders (optional) – Object. This object allows you to add custom request headers. This object consists of "key": "value" pairs, where "key" is a header name and "value" is its value. Check out a live sample on JSFiddle. Important note: requestHeaders is not saved when obtaining the report via save() and getReport() API calls.

Here is an example of how the connection to SSAS via XMLA is represented in dataSource:

{
    dataSource: {
        type: "microsoft analysis services",
        proxyUrl: "http://olap.flexmonster.com/olap/msmdpump.dll", // URL to msmdpump.dll
        catalog: "Adventure Works DW Standard Edition",
        cube: "Adventure Works",
        localeIdentifier: 1036, // Microsoft Locale ID Value for French
        roles: "admin,manager", // roles from SSAS
        subquery: "select {[Delivery Date].[Calendar].[Calendar Year].&[2008]} on columns from [Adventure Works]"
    }
}

Check it out on JSFiddle.

Here is an example of how the connection to SSAS via Flexmonster Accelerator is represented in dataSource:

{
    dataSource: {
        type: "microsoft analysis services",
        proxyUrl: "http://localhost:50005",
        catalog: "Adventure Works DW Standard Edition",
        cube: "Adventure Works",
        binary: true,
        localeIdentifier: 1036, // Microsoft Locale ID Value for French
        subquery: "select {[Delivery Date].[Calendar].[Calendar Year].&[2008]} on columns from [Adventure Works]"
    }
}

You can read all the details about the Accelerator here.

Mondrian

Here is a list of dataSource properties used to connect to Mondrian:

• catalog – String. The data source catalog name.
• cube – String. The given catalog’s cube’s name.
• dataSourceInfo – String. The service info.
• type – String. The type of data source. In this case it is "mondrian".
• proxyUrl – String. The path to the proxy URL.
• binary (optional) – Boolean. A flag to use Flexmonster Accelerator instead of the XMLA protocol.
• roles (optional) – String. A comma-delimited list of predefined roles to connect to a server or a database using the permissions defined by that role. If this property is omitted, all roles are used and the effective permissions are the combination of all roles. For example, to combine "admin" and "manager" roles, set the roles property like so: roles: "admin,manager".
• requestHeaders (optional) – Object. This object allows you to add custom request headers. This object consists of "key": "value" pairs, where "key" is a header name and "value" is its value. Check out a live sample on JSFiddle. Important note: requestHeaders is not saved when obtaining the report via save() and getReport() API calls.

Here is an example of how the connection to Mondrian via XMLA is represented in dataSource:

{
    dataSource: {
        type: "mondrian", // URL to the XMLA provider
        proxyUrl: "http://olap.flexmonster.com:8080/mondrian/xmla",
        dataSourceInfo: "MondrianFoodMart",
        catalog: "FoodMart",
        cube: "Sales"
    }
}

Try the example on JSFiddle.

Here is an example of how the connection to Mondrian via Flexmonster Accelerator is represented in dataSource:

{
    dataSource: {
        type: "mondrian",
        proxyUrl: "localhost:50006",
        dataSourceInfo: "MondrianFoodMart",
        catalog: "FoodMart",
        cube: "Sales",
        binary: true,
        roles: "California manager" // Mondrian roles
    }
}

You can read all the details about the Accelerator here.

Elasticsearch

Here is a list of dataSource properties used to connect to Elasticsearch:

• type – String. The type of data source. In this case it is "elasticsearch".
• subquery (optional) – Bool Query Object. The parameter to set a server-side filter to decrease the size of the response from the server.
• node (optional) – String|Object. The host for the connection. Can be set either as a URL string ("node": "https://olap.flexmonster.com:9200") or as an object with the following properties:
  • protocol – String. node URL protocol.
  • host – String. node URL hostname.
  • port – Number. node URL port.
  • path (optional) – String. node URL path.
• index (optional) – String. The name of Elasticsearch index to connect.
• requestHeaders (optional) – Object. This object allows you to add custom request headers. This object consists of "key": "value" pairs, where "key" is a header name and "value" is its value. Check out a live sample on JSFiddle. Important note: requestHeaders is not saved when obtaining the report via save() and getReport() API calls.
• mapping (optional) – Object. An additional setting to configure index mapping. Use the name of the field as a key of the object with the following parameters:
  • caption (optional) – String. Overrides the default name of the field.
  • visible (optional) – Boolean. When set as false, hides the field from the Field List.
  • interval (optional) – String. Used for date histogram. Check out supported time units.
  • time_zone (optional) – String. Used for date histogram. You can specify timezones as either an ISO 8601 UTC offset (e.g. +01:00 or -08:00) or as a timezone ID as specified in the IANA timezone database, such as`America/Los_Angeles`. Check out the example.
  • format (optional) – String. Used for date histogram. Check out date format/pattern.
  • min_doc_count (optional) – Number. Used for date histogram. Can be used to show intervals with empty values (min_doc_count: 0). Default value: 1 (empty intervals are hidden).

Here is an example of how the connection to Elasticsearch is represented in dataSource:

{
    dataSource: {
        type: "elasticsearch",
        node: "https://olap.flexmonster.com:9200",
        index: "fm-product-sales"
    }
}

Try the example on JSFiddle.

SQL databases

Here is a list of dataSource properties used to connect to SQL databases using the Data Compressor:

• type – String. The type of data source. In this case it is "ocsv".
• filename – String. The URL to the server-side script which generates data.
• requestHeaders (optional) – Object. This object allows you to add custom request headers. This object consists of "key": "value" pairs, where "key" is a header name and "value" is its value. Check out a live sample on JSFiddle. Important note: requestHeaders is not saved when obtaining the report via save() and getReport() API calls.

Flexmonster Data Compressor returns data in OCSV (Optimized CSV) format so you need to define type explicitly:

{
    dataSource: {
        type: "ocsv",
        /* URL to the Data Compressor Node.js, .Net, Java, or PHP */
        filename: "http://localhost:55772/api/flexmonster/get"
    }
}

Read more about the Data Compressor here.

CSV data sources

CSV data source can be:

• A file from the local file system
• A remote static file
• Data generated by a server-side script

Here is a list of dataSource properties used to connect to CSV data sources:

• browseForFile – Boolean. Defines whether you want to load a file from the local file system (true) or not (false). Default value: false.
• type – String. The type of data source. In this case it is "csv". You do not need to explicitly define this property when reading static CSV files with a “.csv” extension.
• fieldSeparator – String. Defines the specific fields separator to split each CSV row. There is no need to define it if the CSV fields are separated by , or ;. This property is required only if another character separates fields. For example if you use TSV, where a tab character is used to separate fields, then the fieldSeparator parameter should be set to "\t".
• thousandSeparator (optional) – String. Defines specific character used to separate groups of digits in numbers. For example, to import CSV data with commas used to separate groups of digits in numbers (e.g. 1,000 for one thousand), set thousandSeparator parameter as ",".
• filename – String. The URL to the file or to the server-side script which generates data.
• ignoreQuotedLineBreaks (from v2.1) – Boolean. Indicates whether line breaks in quotes should be ignored (true) or not (false). Default value: true – this makes CSV parsing faster. Set it to false only if your data source has important line breaks in quotes. Note that this might slow down CSV parsing a little bit.
• recordsetDelimiter – String. Defines which character is used in CSV to denote the end of a CSV row. Default value: "\n".
• requestHeaders (optional) – Object. This object allows you to add custom request headers. This object consists of "key": "value" pairs, where "key" is a header name and "value" is its value. Check out a live sample on JSFiddle. Important note: requestHeaders is not saved when obtaining the report via save() and getReport() API calls.

In the following example data is taken from a CSV file where the colon character (:) is used to separate fields within the row. Line breaks in quotes are not ignored:

{
    dataSource: {
        /* URL or local path to a CSV file */
        filename: 'colon-data.csv',
        fieldSeparator: ':',
        ignoreQuotedLineBreaks: false
    }
}

If the data is generated by a server-side script, type must be defined explicitly:

{
    dataSource: {
        type: "csv",
        filename: "script_which_returns_csv_data"
    }
}

JSON data sources

JSON data source can be:

• Files from the local file system
• A remote static file
• Data generated by a server-side script
• Inline JSON

Here is a list of dataSource properties used to connect to JSON data sources:

• browseForFile – Boolean. Defines whether you want to load the file from the local file system (true) or not (false). Default value: false.
• data (from v2.2) – JSON. The inline JSON data.
• type – String. The type of data source. In this case it is "json". You do not need to explicitly define this property when reading static JSON files with a “.json” extension.
• filename – String. The URL to the file or to the server-side script which generates data.
• requestHeaders (optional) – Object. This object allows you to add custom request headers. The object consists of "key": "value" pairs, where "key" is a header name and "value" is its value. Check out a live sample on JSFiddle. Important note: requestHeaders is not saved when obtaining the report via save() and getReport() API calls.

Here is an example of JSON data set using a file from the local file system:

{
    dataSource: {
        /* Path to the local JSON file */
        filename: "data.json"
    }
}

If the data is generated by a server-side script, type must be defined explicitly:

{
    dataSource: {
        type: "json",
        filename: "script_which_returns_json_data"
    }
}

Inline JSON:

{
    dataSource: {
        /* jsonData variable contains JSON data */
        data: jsonData
    }
}

Change the data source using the Toolbar

Use the Connect option to choose another data source or Open to load another report at runtime. Use Save to save the report with the current data source.

Data in the pivot table will be updated and saved within the report.

Data source via API

The API calls connectTo(), load(), and open() are used to change the data source at runtime. The API call save() is used to save the report.