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. Save and restore the report
    2. Share the report
    3. 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

Managing data presentation in JSON

We recommend using mapping to customize the presentation and structure of JSON data.

The mapping supports:

  • Setting data types in JSON.
  • Specifying a list of aggregations available for a field.
  • Hiding UI filters for a specific field.
  • Formatting a certain date field.
  • And many other configs.

Additionally, the mapping allows separating your data from its representation.

For details on setting the mapping, see our guide.

Alternatively, the first object of the input JSON array can be used for these needs.

Here is the list of its supported properties:

  • type – String. The data type. Can be:
    • "string" – the field contains string data. The field’s members will be sorted as strings.
    • "number" – the field contains numeric data. You will be able to aggregate it with all available aggregations. It will be sorted as numeric data.
    • "month" – the field contains months. Note that if the field stores month names only (in either short or full form), the field will be recognized by Flexmonster as a field of the "month" type automatically. If the field contains custom month names, specify its type as "month" explicitly.
    • "weekday" – the field contains days of the week.
    • "date" – the field is a date. Such fields will be split into 3 different fields: Year, Month, Day.
    • "year/month/day" – the field is a date. You will see such dates as hierarchies: Year > Month > Day.
    • "year/quarter/month/day" – the field is a date. You will see such dates as hierarchies: Year > Quarter > Month > Day.
    • "date string" – the field is a date. Such fields will be formatted using a date pattern (default is "dd/MM/yyyy").
    • "datetime" – the field is a date (numeric data). Such fields will be formatted using "dd/MM/yyyy HH:mm:ss" pattern. Min, max, count, and distinctcount aggregations can be applied to it.
    • "time" – the field is a time (numeric data). Such fields will be formatted using "HH:mm:ss" pattern.
    • "id" – the field is an id of the record. Such fields are used for editing data. This field will not be shown in the Field List.
    • "property" – the field for setting member properties. This field will not be shown in the Field List. For example, it can be used to associate a productID with a productSee the example.
  • hierarchy – String. The hierarchy’s name. When configuring hierarchies, specify this property to mark the field as a level of a hierarchy or as a member property of a hierarchy (in this case, the type parameter should be set to "property").
  • parent – String. The unique name of the parent level. This property is necessary to specify if the field is a level of a hierarchy and has a parent level.
  • isMeasure (optional) – Boolean. When set to true, the field can be selected only as a measure. The isMeasure property should be used only with the strictDataTypes option. Default value: false.

For example, you can add the following first object in a JSON array and see how it changes the report:

var jsonData = [
{
"Color": {type: "string"},
"Country": {
type: "string",
hierarchy: "Geography"
},
"State": {
type: "string",
hierarchy: "Geography",
parent: "Country"
},
"City": {
type: "string",
hierarchy: "Geography",
parent: "State"
},
"Price": {type: "number"},
"Quantity": {type: "number"}
},
{
"Color" : "green",
"Country" : "Canada",
"State" : "Ontario",
"City" : "Toronto",
"Price" : 174,
"Quantity" : 22
},
{
"Color" : "red",
"Country" : "USA",
"State" : "California",
"City" : "Los Angeles",
"Price" : 166,
"Quantity" : 19
}
];

var pivot = new Flexmonster({
container: "pivotContainer",
toolbar: true,
report: {
dataSource: {
data: jsonData
},
slice: {
rows: [
{ uniqueName: "Color" },
{ uniqueName: "[Measures]" }
],
columns: [
{ uniqueName: "Geography" }
],
measures: [
{ uniqueName: "Price", aggregation: "sum" }
]
}
}
});

Try it on JSFiddle.

Note: if you use a JSON array of arrays you can also add the first object. In this case, you do not need to specify hierarchies in the first sub-array. Check out a live example.

Automatic type selection in JSON

Flexmonster selects field types automatically. If needed, you can define only necessary types of fields in both mapping and the first JSON object.

In the example below, only the type of "Date" is set explicitly. Types of "Country" and "Price" will be set automatically as "string" and "number", respectively:

var jsonData = [
{
"Date": { type: "date string" }
},
{
"Date" : "2021-05-25",
"Country" : "Canada",
"Price" : 174
},
{
"Date" : "2021-03-18",
"Country" : "USA",
"Price" : 166
}
];

var pivot = new Flexmonster({
container: "pivotContainer",
toolbar: true,
report: {
dataSource: {
data: jsonData
}
}
});

Supported date formats

To make date fields be interpreted as a date, you must define the data type as a date. For example, "type": "date", "type": "date string", "type": "datetime", "type": "year/month/day" or "type": "year/quarter/month/day". Additionally, data from these fields should have a special date format to be understood properly.

Flexmonster supports the following input date formats:

  1. ISO 8601. For example:
    • "2021-04-25" – Date.
    • "2021-04-25T21:30:05" – Date and time.
    • "2021-04-25T21:30:05+03:00" – Date and time with a time zone.
  2. Unix timestamp. For example, "2021-04-25" will be 1619298000 in the Unix timestamp format.
    Note that it is important to assign the date type to the Unix timestamp field explicitly. Otherwise, the component will treat this field as a numeric one.

Other formats aren’t officially supported and may have unexpected results.