Pricing changes are coming in January. Contact our Sales team to secure the current price for your desired license.

[bug] field values casing causes missing data

Answered
brian mulh asked on November 8, 2024

Hello,

There appears to be a bug when using the custom data API with field values that are the same but have different casing(ie "john, smith" vs "JOHN, SMITH").  It appears the flexmonster UI will only display one of these values and throw out the other.

I have provided an example dataset CSV and flexmonster configuration that can reproduce this bug:

- example video

- dataset

- flexmonster config

- select response

In this example there are two distinct names where the only difference is upper case vs lower case.  In the video you can see that the pivot is only showing one name at that name level and the values for name are not adding up to the aggregate "income_statement_level" because the pivot has thrown out one of the names.  Under "Other" I'd expect two names that add up to $15 but I am only seeing a single row that adds up to $5.

In the select response you can see that I am correctly returning the values for both names so it appears the pivot is incorrectly picking one rather than displaying both.  Would you be able to fix the flexmonster UI to allow for differences in casing still displaying both values?

Thanks,

Brian

 

 

3 answers

Public
Nadia Khodakivska Nadia Khodakivska Flexmonster November 11, 2024

Hello Brian,

Thank you for reaching out to us.

Kindly note that members are not case-sensitive in Flexmonster by default. However, you can set the caseSensitiveMembers property of the Options object to true to make the field members case-sensitive. You are welcome to check the following example for reference: https://jsfiddle.net/flexmonster/tgzqr7pm/.

Please let us know if it works for you. Looking forward to hearing from you.

Kind regards,
Nadia

Public
brian mulh November 11, 2024

Nadia,

 

Thank you, using caseSensitiveMembers did fix our issue.  It is a bit concerning that the default is set to `false` which causes it will throw out values at the lower level and then the pivot table does not add up when aggregating lower levels of the pivot.  At the very least I'd expect it to merge the values together and still correctly add up.  Given that it doesn't we will make sure to use caseSensitiveMembers going forward.

 

Thanks,

Brian

Public
Nadia Khodakivska Nadia Khodakivska Flexmonster November 12, 2024

Hi Brian,

Thank you for the feedback!

Feel free to contact us if other questions arise.

Kind regards,
Nadia

Please login or Register to Submit Answer