I have an issue with the totals on a row. It does not always show the correct amount as you can see in the attachment.
As datasource i use Elastic Search 6.8 and i use the latest Flexmonster version. I have set up a test environment in Elastic Search. I will email this info to support.
Thank you for writing to us and providing detailed information about the issue.
Our team noticed that in the Elasticsearch response there are keys that differ only by the case of the first letter. For example, “standup” and “Standup”. Flexmonster combines their values into 1 row but shows totals in an unexpected way.
If the case of letters should not be taken into account, please store your data within a single register.
Otherwise, we would like to kindly suggest defining the property
caseSensitiveMembers of the Options Object as
true, so the component will treat the mentioned keys as different. Please have a look at the example: https://jsfiddle.net/flexmonster/rezoutja/.
Please let us know if it works for you and if you have any additional questions.
Thanks for your reply.
Since we do not know if the user means “standup” or “Standup” the values must be treated as different values. Setting the property “caseSensitiveMembers” does the trick here.
I will remove the test environment.
I have a similar case:
It looks like Flexmonster distincts the value of a column and then sums the values for these columns, for instance:
record1 = c1:”Column test 1″ and c2: “2”
record2 = c1:”Column test 1″ and c2: “3”
Column c1 has almost the same value in both records, but in record2 there is an extra space between the text “Column” and “test”
It looks like Flexmonster thinks these are the same values and distincts them, and then sums the value for them…..but the first value “Column test 1” can only be found once in the records and will sums the value 2…..
So the result is:
“Column test 1” and “2”
Total: 5 >>> yes, it shows the sum of both values in the row total
while it should have been:
“Column test 1” and “2”
“Column test 1” and “3”
Could you help with this situation?
Thank you for posting your question.
We’ve tested a similar Elasticsearch dataset on our side with the latest Flexmonster version (2.8.32).
Everything seems to be working correctly on our side, except for the member with an extra space being displayed without it (see attached screenshot for illustration), which we are going to fix with our upcoming release ETA Jun 14th.
That being said, we’d suggest updating to the latest Flexmonster version to see whether the issue you’re referring to persists.
Please let us know if this helps.
We also use the 2.8.32 and the issue still exists. I will await the new version to see if the fix for the space not being displayed will also fix our issue.
Hope you’re doing well!
We’ve introduced a fix addressing the issue with showing two and more spaces in the member names on the grid.
This is available in the 2.9.1 version of Flexmonster: https://www.flexmonster.com/release-notes/.
You are welcome to update the component. Here is our updating to the latest version guide for assistance: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
How are you?
Have you had a chance to test out our latest fix?
We would be happy to hear your feedback.