asked on February 28, 2022
Hi,
we have some issue with report filters, we have some custom logic for prefill filter.
We set report cfg as
{
....
"slice": {
"reportFilters": [{
"uniqueName": "[01 - Selezione Periodo].[Anno]",
"filter": {
"members": [
"[01 - Selezione Periodo].[Anno].&[2021]"
]
}
}, {
"uniqueName": "[01 - Selezione Periodo].[Data Del Giorno]",
"filter": {
"members": [
"[01 - Selezione Periodo].[Data Del Giorno].&[02/01/2021]"
]
}
},
...
}
For dimension "Anno" filter works properly but for "Data Del Giorno" filter is not set (img_001).
I try to investigate with methods "setFilter" and "getFilter" but also in this case we have the same issue.
If i set filter from UI it works, but i try to get value with "getFilter" and set the same value with "setFilter" it not works.
In console i have warning:
main.js:1 Error in predefined filter or members have not been loaded yet: [01 - Selezione Periodo].[Data Del Giorno].&[02/01/2021]
We are using:
- ng-flexmonster: 2.9.19
- accelerator 2.9.19
Best Regards
⋅ March 1, 2022
Hi, Marius!
Thank you for reaching out to us!
The described error message is not reproducible on our side.
Our supposition is that the data member is not set correctly. Please try setting filter via UI and then save the config. It should contain the correct name of the member.
Please let us know if it works for you.
Best Regards,
Maksym
⋅ March 23, 2022
Hi Maksym,
i try exactly in that way, but the problem is still present.
For export report cfg and save we use "fmInstance.getReport()" for set report config we use "report" input of the <fm-pivot> element.
PS: In the while we have update the version to 2.9.21
⋅ March 25, 2022
Hi, Marius!
Thank you for providing more context.
Kindly note that our team recently fixed a similar issue with report filters. Please refer to this support ticket for more details.
As for now, we were unable to reproduce the issue on the latest version of Flexmonster, using our sample data. Could you please modify the sample project in the attachments below so the issue is reproducible? This will help our team to understand the situation better and help you solve the problem.
Thank you, and looking forward to hearing from you.
Best Regards,
Maksym
⋅ March 28, 2022
Hi Maksym,
i can reproduce error simple change "getReport()" method with:
{
"dataSource": {
"type": "microsoft analysis services",
"proxyUrl": "https://olap.flexmonster.com/olap/msmdpump.dll",
"catalog": "Adventure Works DW Standard Edition",
"cube": "Adventure Works",
"binary": false
},
"slice": {
"reportFilters": [
{
"uniqueName": "[Ship Date].[Calendar]",
"caption": "Ship Date.Calendar"
},
{
"uniqueName": "[Ship Date].[Date]",
"caption": "Ship Date.Date",
"filter": {
"members": [
"[Ship Date].[Date].&[20130210]"
]
}
}
],
"rows": [
{
"uniqueName": "[Geography].[Country]"
}
],
"columns": [
{
"uniqueName": "[Measures]"
}
],
"measures": [
{
"uniqueName": "[Measures].[Internet Order Count]"
}
]
},
"version": "2.9.21",
"creationDate": "2022-03-28T14:54:18.787Z"
}
}
⋅ March 29, 2022
Hi, Marius!
Thank you for providing a report example.
Though we did not see any warnings in console, the issue is reproducible on our side. Our team will provide a fix with our minor release with the ETA April 18th.
Please stay tuned, we will notify you when the fix is ready.
Best Regards,
Maksym
⋅ April 19, 2022
Hello, Marius!
We are glad to announce that the issue with report filters while using the XMLA protocol was fixed.
This update is included in the 2.9.23 version of Flexmonster:https://www.flexmonster.com/release-notes/version-2923/
You are welcome to update the component. Here is our guide on upgrading to the latest version: https://www.flexmonster.com/doc/updating-to-the-latest-version/
Feel free to contact us if any questions arise.
Best Regards,
Solomiia
⋅ April 26, 2022
Hello, Marius!
Hope you are having a great week.
Could you please confirm that the fix with report filters works well for you?
Looking forward to hearing from you.
Regards,
Solomiia.
⋅ May 2, 2022
Hi Solomiia,
we had update the component, but we still have the problem... but now i can't reproduce the issue on "example project".
The main difference between "example project" and "our project" is the accelerator. In our project we are using the accelerator (binary: true)
⋅ May 4, 2022
Hello, Marius,
Thank you for the response.
Our team had one more round of detailed investigation and finally reproduced the issue specifically using Accelerator. We will provide a fix with our minor release with the ETA May 16th.
Feel free to contact us if any questions arise.
Kind regards,
Nadia
⋅ May 17, 2022
Hello, Marius,
We are glad to inform you that the issue with a report filter initialization for the Flexmonster Accelerator was fixed.
This fix is available in the 2.9.25 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2925/
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/
Please let us know if any questions arise.
Kind regards,
Nadia
⋅ May 25, 2022
Hello, Marius,
Hope you are doing well.
We were wondering if you had a chance to test the fix.
Looking forward to hearing your feedback.
Kind regards,
Nadia
⋅ May 26, 2022
Hi Nadia,
now it works. After the 2.9.25 update we can not reproduce the issue =).
Thanks, and sorry for the late reply,
Kind regards,
Marius
⋅ May 26, 2022
Hello, Marius,
Thank you for the feedback!
We are happy to hear that it works well for you.
As always, feel free to contact us in case further questions arise.
Kind regards,
Nadia