🍉 Meet Flexmonster Pivot Table & Charts 2.9.Check out all the hot features!
Get Free Trial

What’s changed between 2.8.4 and 2.8.5 and later releases

Answered
Toni Laukka asked on December 10, 2020

We have been trying to update from 2.7.22 to latest version of Flexmonster. We get blank reports with the latest version and found out that version 2.8.4 shows our reports correctly but after updating to 2.8.5 we started getting blank reports.

Data is exactly same, but slice is missing rows and some measures.
 
Screenshot 2020-12-10 at 15.51.25.png is the slice from 2.8.5

5 answers

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster December 14, 2020

Hello, Toni,
 
Thank you for giving us some time.
 
We did not manage to reproduce this problem on our side.
Please send us the complete report with the data (use dummy records if needed) in JSON format.
It would allow us to reproduce the problem on our side and find possible causes for this behavior.
 
Our team is looking forward to hearing from you.
 
Regards,
Illia

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster December 23, 2020

Hello, Toni,
 
Our team is reaching out to ask if you had some time to prepare the mentioned reports.
 
We are looking forward to hearing from you.
 
Regards,
Illia

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster January 11, 2021

Hello, Toni,
 
We are wondering if you are still facing the issue with incompatible reports.
If so, please provide us with corresponding report samples that would demonstrate the problem.
 
Our team is looking forward to hearing from you.
 
Regards,
Illia

Public
Toni Laukka January 15, 2021

Yes. We are still facing the same issue. It works fine on version 2.8.4, but not after that. I tried today with version 2.8.24 but the issue remains. I’ve attached a sample json.

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster January 18, 2021

Hello, Toni,
 
Thank you for providing us with a report.
It did manage to bring some light on the nature of the problem.
 
We want to explain that the report contains several unexpected constructions that prevent it from being correctly displayed in the component. The reason for the correct display before version 2.8.4 was less strict validation of the reports.
 
We suggest considering the following correction to make the report work with the latest Flexmonster versions:

  • The hierarchy property is used to specify multilevel hierarchies. Every level of the hierarchy also must have a parent property as described in our documentation. We suggest either specifying the parent property for each level of the following hierarchies or deleting the hierarchy completely:
    "company": {
        "type": "string",
        "hierarchy": "cols"
    },
    "datasource": {
        "type": "string",
        "hierarchy": "cols"
    },
    ...
    "date": {
        "type": "string",
        "hierarchy": "cols"
    },
    "accountingPeriod": {
        "type": "string",
        "hierarchy": "",
        "dimensionUniqueName": "Data Property"
    },
    "isBudgetData": {
        "type": "string",
        "hierarchy": "",
        "dimensionUniqueName": "Data Property"
    },
    ...
    
  • The dimensionUniqueName property was deprecated in version 2.8.23. Now the folder property from the mapping should be used. Still, you can use this property for older reports because of the backward compatibility.
  • The way to specify multilevel hierarchies was simplified. Now, the type and level properties may be omitted. For example:
    "level1": {
        "type": "level",
        "level": "Level1",
        "hierarchy": "rows"
    },
    "level2": {
        "type": "level",
        "level": "Level2",
        "parent": "level1",
        "hierarchy": "rows"
    },
    "level3": {
        "type": "level",
        "level": "Level3",
        "parent": "level2",
        "hierarchy": "rows"
    },
    ...
    

    Still, you can use this style of defining multilevel hierarchies because of the backward compatibility.

  • Finally, we do not recommend to specify fields that are not presented in the data set (for example, “level4” and “level4” fields).

 
You are welcome to see the JSFiddle that demonstrates all these corrections.
 
Please let us know if it works for you.
Feel free to contact us if other questions arise.
 
Kind regards,
Illia

Please login or Register to Submit Answer