asked on January 31, 2025
I set a custom name for the blank columns with:
localization: {
grid: {
blankMember: "No Pivot"
}
},
and its generally working but sometimes for no obvious reason just switching back to blank. Do you know what could be going wrong? On the screenshot I keep expanding column by column and everything is good until I expand Column 35 when suddenly it switches back to (blank). Here is full report definition:
report: {
dataSource: {
data: ret.data,
mapping: scil.Registration.FlexViewer.getmapping(ret)
},
options: {
grid: {
showTotals: "off",
},
},
formats: [
{
name: "customnumber",
...scil.Registration.FlexViewer.digitformat
}
],
slice: {
columns: scil.Registration.FlexViewer.getcols(ret),
rows: scil.Registration.FlexViewer.getrows(ret),
measures: scil.Registration.FlexViewer.getmeasures(ret)
},
localization: {
grid: {
blankMember: "No Pivot"
}
},
}
⋅ February 3, 2025
Hello,
Thank you for contacting us.
We recently encountered a similar issue with localization when using the updateData API call. Our team will provide a fix with our minor release with the ETA February 17th. Could you please confirm if the custom name for the blank column disappears when the updateData method is called? It would greatly help us.
As a temporary workaround, we recommend setting localization in the GlobalObject. For example:
const pivot = new Flexmonster({
container: "#pivot-container",
global: {
localization: {
grid: {
blankMember: "No Pivot"
}
}
},
// other properties
})
Please check our documentation for more details: https://www.flexmonster.com/doc/localizing-component/#set-a-localization.
Looking forward to hearing from you.
Kind regards,
Nadia
⋅ February 10, 2025
Hi Nadia,
Yes, when updateData() is called it changes back to (blank).
Thank you!
⋅ February 11, 2025
Hello,
Thank you for the response.
Our team will notify you about the fix in our minor release.
You are welcome to contact us if further questions arise.
Kind regards,
Nadia
⋅ 5 days ago
Hello,
We are pleased to inform you that the issue with localization being cleared on the updateData() call was fixed.
This fix is provided in the 2.9.97 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-97
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/
Please tell us if the fix works. Looking forward to hearing your feedback.
Kind regards,
Nadia