asked on January 30, 2026
Hello,
We use the custom data API and sometimes when removing columns from the drillthrough, it will send the hierarchy name as a field in the select request. This causes an error on the backend. I have attached a video of this occurring. Here is an example.
The issue may be due to the fact we have a hierarchy named similar to a field name. Here is what the mapping looks like
"mapping": {
"CONTRIBUTION_MARGIN": {
"type": "string",
"hierarchy": "Contribution Margin",
"caption": "Contribution Margin"
},
"CONTRIBUTION_MARGIN_CATEGORY": {
"type": "string",
"hierarchy": "Contribution Margin",
"caption": "Contribution Margin Category",
"parent": "CONTRIBUTION_MARGIN"
},
"CONTRIBUTION_MARGIN_ACCOUNT": {
"type": "string",
"hierarchy": "Contribution Margin",
"caption": "Contribution Margin Account",
"parent": "CONTRIBUTION_MARGIN_CATEGORY"
}
}
We do that so we can nest all the expand/collapse the "Contribution Margin" row. Is there a better way to do this or can you fix the drillthrough issue to not send the hierarchy name in the select request?
Thanks,
Brian
⋅ February 2, 2026
Hello, Brian,
Thank you for reporting this issue.
We could not reproduce this behavior on our side using a similar hierarchy setup. As a first step, we recommend updating to the latest version of Flexmonster, as the issue may have already been addressed. If it persists in the latest version, could you please modify this sample so that it is reproducible there: https://jsfiddle.net/flexmonster/w8p32bsn/
Having a reproducible example will help us investigate the issue further and provide a more accurate solution.
We are looking forward to hearing from you.
Best regards,
Maksym
⋅ 3 hours ago
Hello, Brian,
Hope you are doing well.
We are wondering whether updating Flexmonster helped you resolve the issue of sending the incorrect name in the /select requests for drill-through. If not, could you provide more details or steps to reproduce this behavior?
Looking forward to hearing from you.
Best regards,
Maksym
