When using “showEmptyValues” without using a hierarchy it generates a lot children that is not needed:
In the following fiddle: https://jsfiddle.net/0jac31rn/
“49_Gross Margin” belongs to the account “48_Operating Profit” however when using “showEmptyValues: true” it is also added to “88_Other Income and Expense” with it has no affiliation with.
Thank you for raising this support ticket and for preparing the JSFiddle.
You are right about the fact that Flexmonster creates extra intersections when using the
showEmptyValues property. It is because both empty and non-existing intersections are equal in the internal representation.
Currently, this behavior cannot be changed.
Please let us know if other questions arise.
How come this behavior not happen in multilevel hierarchies?
Shouldn’t the setting have the same outcome?
Thank you for your question.
When building the multilevel hierarchy, Flexmonster recursively analyzes members of each level to build up the internal structure. It means that all the existing intersections are known right after the report initialization. As a result, Flexmonster does not display non-existing tuples when the
showEmptyValues property is set to
Consider using multilevel hierarchies if this behavior is preferred for your case.
Feel free to reach out if other questions arise.