Flexmonster Software License Agreement (“Agreement”) has been significantly revised and is effective as of September 30, 2024.
The following modifications were made:
The modified version of Flexmonster Software License Agreement is available here.
Downloading, installing, and/or continuing to use Flexmonster Software after September 30, 2024, constitutes Licensee’s acceptance of the terms and conditions of the modified version of Flexmonster Software License Agreement. If Licensee does not agree to any of these terms and conditions, they must cease using Flexmonster Software and must not download, install, use, access, or continue to access Flexmonster Software. By continuing to use Flexmonster Software or renewing the license under License Model or Maintenance after the effective date of any modifications to Agreement, Licensee accepts and agrees to be bound by the terms and conditions of the modified Agreement.
In this guide, you can find solutions to errors that you might experience while working with Flexmonster Pivot. If your error is not listed here, contact our technical support.
If you are facing any integration issues, open developer tools on the page with Flexmonster:
Ctrl + Shift + I or F12.Command + Option + I.Then go to the console and check if it shows any errors. If so, look for solutions to the errors in this section.
The flexmonster.js file was not loaded successfully. Ensure that the correct path to flexmonster.js is specified. It depends on how you have downloaded Flexmonster:
<script src="node_modules/flexmonster/flexmonster.js"></script>
<script src="https://cdn.flexmonster.com/flexmonster.js"></script>
<script src="flexmonster/flexmonster.js"></script>
The new Flexmonster() API call was used to embed the component, but the flexmonster.js file was not loaded successfully. This may be caused by one of the following:
flexmonster.js is correct. The path to flexmonster.js depends on how you have downloaded Flexmonster:<script src="node_modules/flexmonster/flexmonster.js"></script>
<script src="https://cdn.flexmonster.com/flexmonster.js"></script>
<script src="flexmonster/flexmonster.js"></script>
flexmonster.js from remote resources (e.g., CDN). Check your internet connection status.flexmonster.js. Make sure that the current user has enough privileges.Flexmonster embedding failed since the flexmonster.js file was not loaded successfully. Check the following:
flexmonster.js, depending on how Flexmonster was downloaded:<script src="node_modules/flexmonster/flexmonster.js"></script>
<script src="https://cdn.flexmonster.com/flexmonster.js"></script>
<script src="flexmonster/flexmonster.js"></script>
This error appears in Internet Explorer 11 because IE does not support the ES6 standard used by Flexmonster. Learn more in our blog post: Flexmonster stops providing the ECMAScript 2009 (ES5) version of the product.
The container parameter is missing from the new Flexmonster() API call. Set the container parameter as follows:
<div id="pivotContainer">Flexmonster will appear here</div>
<script>
const pivot = new Flexmonster({
container: "pivotContainer",
// Other parameters
});
</script>
There is no HTML element with the id specified in the new Flexmonster()’s container parameter ([container id]). Make sure an element with the [container id] id exists.
The contents of the flexmonster/ folder were not loaded successfully. Ensure that the correct path to flexmonster/ is specified in the componentFolder parameter. The path to flexmonster/ depends on how you have downloaded Flexmonster:
const pivot = new Flexmonster({
container: "pivotContainer",
componentFolder: "node_modules/flexmonster/",
// Other parameters
});
const pivot = new Flexmonster({
container: "pivotContainer",
componentFolder: "https://cdn.flexmonster.com/",
// Other parameters
});
const pivot = new Flexmonster({
container: "pivotContainer",
componentFolder: "flexmonster/",
// Other parameters
});
The contents of the flexmonster/ folder with all Flexmonster files (including flexmonster.css) were not loaded successfully. Ensure that the correct path to flexmonster/ is specified in the componentFolder parameter. The path to flexmonster/ depends on how you have downloaded Flexmonster:
const pivot = new Flexmonster({
container: "pivotContainer",
componentFolder: "node_modules/flexmonster/",
// Other parameters
});
const pivot = new Flexmonster({
container: "pivotContainer",
componentFolder: "https://cdn.flexmonster.com/",
// Other parameters
});
const pivot = new Flexmonster({
container: "pivotContainer",
componentFolder: "flexmonster/",
// Other parameters
});
The theme/assets/ folder is missing from the flexmonster/ folder. To fix this, remove Flexmonster from your project and download it again.
The toolbar/ folder is missing from the flexmonster/ folder and toolbar: true was specified when embedding the component. To fix this, remove Flexmonster from your project and download it again.
Errors like this may appear in the console if the lib/ folder is missing from the flexmonster/ folder or if the necessary file was removed from lib/.
To get rid of such errors, remove Flexmonster from your project and download it again.
flexmonster.css and flexmonster.js versions do not match. This can happen if flexmonster.css has not been updated along with other Flexmonster files.
Check which JavaScript and CSS versions are specified in the warning's text. Alternatively, you can check flexmonster.css and flexmonster.js versions by viewing these files through the Sources tab in your browser’s developer tools.
See how the version is specified in CSS and JavaScript files:
:root {
--fm-version: "<version>"
}
/** * Flexmonster Pivot Table & Charts * <version> */
If flexmonster.css and flexmonster.js versions are not the same, follow the steps below:
flexmonster.css and flexmonster.js to the same version.flexmonster.css and flexmonster.js versions match.If the warning persists, contact our technical support.
This section lists solutions to errors that may occur with license keys.
Your license key is tied to a specific domain (e.g., example.com) and will not work on any other domain.
Make sure your license key is used on the domain it was issued for (e.g., example.com). If you need a license key for another domain, contact our team.
You are integrating with a third-party charting library while using a trial license key. This key does not support integration with third-party charting libraries. Contact our team to request a special trial key.
For our customers, we recommend replacing the trial key with their development or production license key.
Flexmonster has been updated to the version that is not covered by the license key you are using. To continue using this version, renew your maintenance and get a new license key. Contact our team for assistance. If you are facing this error after the renewal, please ensure that you have updated the license key in the component.
Alternatively, you can downgrade the Flexmonster version to the latest supported version. You can find it in the Maintenance expired pop-up message. If the supported version is not shown in the message, contact our team.
Note that the component might update unexpectedly when:
npm update command is run.To avoid unexpected updates, we recommend locking the Flexmonster version. Steps to lock the version depend on how you have downloaded Flexmonster:
Install the exact Flexmonster version using the --save-exact flag:
npm install flexmonster@2.9.54 --save-exact
Replace a link to the latest Flexmonster version with a link to a specific version:
<script src="https://cdn.flexmonster.com/2.9.54/flexmonster.js"></script>
A development license key is used on a real domain. With the development key, the component can be run only locally on your computer (localhost), on a server using the server’s IP address, or on a .local domain.
To get a license key for the real domain (e.g., example.com), contact our team.
If you already have a key for the real domain, please ensure that you have set the license key for the component.
Your license key has expired. To renew your annual subscription, contact our team.
If you are facing this error after the renewal, please ensure that you have updated the license key in the component.
Your trial license key has expired. To extend the trial period and get a new key, contact our team.
If you have already purchased a Flexmonster license, please ensure that you have set the license key for the component.
Only a part of the license key has been set in the component. Ensure that you have copied the license key correctly.
Only a part of the license key has been set in the component. Ensure that you have copied the license key correctly.
A key placeholder is used instead of a real license key. Replace "XXXX-XXXX-XXXX-XXXX-XXXX" with your actual key.
If you don't have a license key, contact our team.
This message may be caused by one of the following:
An empty license key is used. Please set your actual key in the component.
If you don’t have a license key, contact our team.
Flexmonster has been updated to the version that is not covered by your license maintenance. You should renew your maintenance or downgrade the Flexmonster version. To renew the license maintenance or find out which version you can use, contact our team. If you are facing this error after the renewal, please ensure that you have updated the license key in the component.
Note that the component might update unexpectedly when:
npm update command is run.To avoid unexpected updates, we recommend locking the Flexmonster version. Steps to lock the version depend on how you have downloaded Flexmonster:
Install the exact Flexmonster version using the --save-exact flag:
npm install flexmonster@2.9.54 --save-exact
Replace a link to the latest Flexmonster version with a link to a specific version:
<script src="https://cdn.flexmonster.com/2.9.54/flexmonster.js"></script>
Here you can find solutions to errors that you may face when connecting to the data source or loading data into Flexmonster.
This message may be caused by one of the following:
filename property will not work since JavaScript has no access to the filesystem.filename property.This error may be caused by one of the following:
The catalog or cube name used for the connection to the cube is incorrect. Ensure that you have specified them correctly. To get the exact catalog and cube names, use the Toolbar:
Another possible cause of this error message is an internal server error. Check your browser’s console for any errors. Also, check errors on the server side of your application.
This error may be caused by one of the following:
This error might occur in the Google Chrome browser if you load large JSON or CSV data using the dataSource.filename property.
You can resolve this error in one of the following ways:
true. This allows loading the large data in small chunks.This message may be caused by one of the following:
The specified Elasticsearch index does not exist on your server. Make sure you have specified the correct index in the dataSource.index property.
Starting from version 2.9.26, Flexmonster applies the mapping calendar_interval property to the date fields in the slice by default. The calendar_interval is not available in Elasticsearch versions before 7.2.
If your version of Elasticsearch is older than 7.2 and you are using dates in the slice, specify the interval property in the mapping explicitly to fix the error. For example:
report: {
dataSource: {
type: "elasticsearch",
// Other configs
mapping: {
"YourDateField": {
interval: "day"
}
}
}
}
You are using the mapping fixed_interval property, which is not supported in your version of Elasticsearch. The fixed_interval was added to Elasticsearch in version 7.2 and is not available in older versions.
To fix the error, specify the interval property in the mapping instead of fixed_interval. For example:
report: {
dataSource: {
type: "elasticsearch",
// Other configs
mapping: {
"YourDateField": {
interval: "3h"
}
}
}
}
This issue occurs when your dataset contains dates in a format that is not officially supported by Flexmonster.
To resolve the issue, define dates in a supported format.
If you are using data or localization with non-Latin characters, the following issues might occur:
"?".To resolve such issues, set the UTF-8 encoding for your HTML page. There are two ways to do this:
meta tag on your page:<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
.js file and specify the UTF-8 encoding when referencing it:<script src="yourfile.js" charset="UTF-8"></script>
If you are exporting the report with non-Latin characters to PDF, use the exportTo() method with the params.fontUrl property set to the URL that leads to the necessary TTF font file.
Note Data in a database, a JSON file, or a CSV file must also be encoded as UTF-8.
The fullscreen feature is blocked by the Feature-Policy fullscreen directive sent from your server. To permit fullscreen, add your project’s domain name to the directive’s allow list. For example:
Feature-Policy: fullscreen https://example.com
This issue occurs when you are trying to save the report to a server using the save() API call, but the report is too large to be encoded.
To resolve the issue, set the serverContentType parameter of the save() method to "application/json":
pivot.save({
filename: "report.json",
destination: "server",
url: "https://example.com/",
serverContentType: "application/json"
});
Try the following steps: