Row totals do not always show the correct number

Hi Milena,

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.
Thanks!
I will remove the test environment.
Regards Jaco

Hi support,
 
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"
Total: 5
 
Could you help with this situation?
 
Regards Jaco

Hi Mykhailo,
 
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.
 
Regards Jaco

Hi Mykhailo,
 
I have tested the issue with flexmonster 2.9.1, but unfortunately the issue is still there:
I have 1 column with a value "test 1" and a value "test  1" (2 spaces) and they appear grouped as "test 1" (with 1 space)...but the sum is only the one from "test 1". But the funny part is that the column total sums both values.
 
Regards,
Jaco

Hi Mykhailo,
The last i checked the issue was still there. I will try to check it this week and if it still persists, i will set up a test environment for you.
At this time we use the following versions:

• Elasticsearch version: 7.10
• Flexmonster version: 2.9.2

 
Regards Jaco

Hi Mykhailo ,
 
I didnt have the time to produce a working environment for you to test this issue. 
I will get back to you next month, to see if its been fixed and if not, i will setup a test environment.
 
Regards Kaco

Hi Mykhailo,
I am not able to produce a working public environment for elasticsearch (due to authentication issues) to show this error.
But i did notice the following:
When we sent data to elastic search (where 1 record has 1 space and the other has 2 spaces), it looks like the double spaces are represented as a single space, therefore, when Flexmonster retrieves this data, it gets the following data:
,"buckets":[
{"key":"test 1","doc_count":1,"sum_f_decltime_f":{"value":2}},
{"key":"test 1","doc_count":1,"sum_f_decltime_f":{"value":1}}]}
There are 2 key entries, but they have the same value, namely "test 1". Flexmonster gets unique keys and takes the summed value of that key. Therefore missing the total summed value.
 
ElasticSearch should have returned
,"buckets":[
{"key":"test 1","doc_count":1,"sum_f_decltime_f":{"value":2}},
{"key":"test  1","doc_count":1,"sum_f_decltime_f":{"value":1}}]}
 
Then (i think) Flexmonster would also have made 2 entries, since there are now 2 unique keys.
 
When both records have "test 1" and we sent that to Elastic Search and flexmonster retrieves this data, then we get:
,"buckets":[
{"key":"test 1","doc_count":2,"sum_f_decltime_f":{"value":3}}]}
 
Now there is 1 key (which is correct, because both keys are with 1 space) and the summed value is now also correct.
 
So, i think that the fault lies mainly with Elasticsearch and the representation of the data. But, if Flexmonster would sum the values of the same key they get returned, then the problem would also be fixed.
 
I hope i have provided you with enough additional information for you to reproduce this issue and make a fix for it.
 
Regards Jaco

Thanks Mykhailo for the follow up and the related threads, i will look into those.
 
Regarding your remark:
If Flexmonster is fed two data entries with keys (and other fields) of the same value, it is only natural that the pivot table treats them as the same record, summing its numeric values
 
The point here, is that Flexmonster indeed does treat them as the same record, but does not sum the values from both records, but seems to use only the value from the first entry.
 
Regards Jaco