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

Can’t apply a unique id to a row when using hierarchy properties or id type

Nick Prodromou asked on October 30, 2020

There appears to be a bug in how flexmonster applies its properties when using mapping, where if the field’s value isn’t unique, then all fields with that value will get the same id, you can see this occurring in my example:
My use case is this:
I need a unique ID for each row, that’s accessible when you click on a customised cell, and I don’t want to show that ID in my table at all. if possible I need multiple of these per row. if not I can use that ID to get the rest of the data from the reportData.
i’ve tried this: https://www.flexmonster.com/question/how-to-hide-a-column-from-report-ui-in-flat-form-and-yet-retrieve-the-value-from-getcell/ but to no avail
I’ve also tried to implement the ‘id’ type, but it has the same problem where if there’s a non-unique value it will use a the id for every other instance of that value (as you can see in my example)
Also using the data.recordId has the same problem.
is it possible to get the values for a whole row, including hidden data inside the customizeCell function?

4 answers

Mykhailo Halaida Mykhailo Halaida Flexmonster November 2, 2020

Hi Nick,
Thank you for posting your question.
We’ve managed to reproduce the described behavior on our side – it seems like a wrong member value is assigned to the cell’s property. Our team will take a look at this and we’ll return to you with a fix ETA Nov 30th.
Please let us know if there is anything else we can help you with in the meantime.
Best regards,

Nick Prodromou November 30, 2020

Hi Mykhalio,

Do you have an update?

Mykhailo Halaida Mykhailo Halaida Flexmonster December 2, 2020

Hi Nick,
We’ve taken a look at the issue you’ve reported, and the following are the results: it is unfeasible to achieve the desired behavior with member properties due to how member properties work from the inside.
Instead, we’ve decided to extend the id field type (recordId) functionality to the frozen cells, allowing us to achieve the necessary results. Therefore, we would suggest using id fields for such purposes – here is a sample illustrating this: https://jsfiddle.net/flexmonster/wzvqb6er/.
This is available in Flexmonster version 2.8.21: https://www.flexmonster.com/release-notes/.
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
Please let us know if this helps.
Best regards,

Mykhailo Halaida Mykhailo Halaida Flexmonster December 9, 2020

Hi Nick,
Hope you’re doing well.
Just checking in to ask if you’ve had a chance to look through our previous response. Have you found it helpful?
We would be happy to hear your feedback.
Kind regards,

Please login or Register to Submit Answer