The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Greetings everyone!
I am trying to export report using the PowerBI Azure SDK exportreport api but while exporting the Date filter using DAX query, am unable to set the date in the calendar date visual if the exported date filter is beyond the max relative date slicer values set in the embedded report. I am attaching some figures to explain better:
Fig_Embedded_Report:
Fig_Exported_Report:
So, here in the 2nd scenario I exported the report with the date filter property which was b/w 2020-2023 but as we can see from cross-referencing with the 1st figure its not taking when exporting.(The DateTable though has no data for 2020 and has from 2021 but even after setting filter b/w 2021-2023 it won't take it if in Embedded View we set the relative slicer to 1 year).
So, is this scenario happening because the max value of relative date slicer is overriding the exportFilter property set when exporting report? (Kindly pardon me if the post seems lengthy or complicated)
Solved! Go to Solution.
Hi @alohaes ,
If I understand correctly, it seems that you can't set the data beyond the max date of calendar visual in the embeded report. It's possible that the behavior you're experiencing is due to the way the report was designed. When a report is embedded, it may be configured to limit certain interactions or features in order to optimize performance or prevent unintended consequences. In this case, it's possible that the report was designed to only allow the calendar date visual to display data within the range of the selected relative date slicer. This would prevent users from inadvertently selecting a date range that is too large and causing the report to slow down or crash. If you have access to the report's design, you may be able to modify this behavior by adjusting the report's settings or editing the code. Otherwise, you may need to contact the report's creator for further assistance.
Best Regards
Hi @alohaes ,
If I understand correctly, it seems that you can't set the data beyond the max date of calendar visual in the embeded report. It's possible that the behavior you're experiencing is due to the way the report was designed. When a report is embedded, it may be configured to limit certain interactions or features in order to optimize performance or prevent unintended consequences. In this case, it's possible that the report was designed to only allow the calendar date visual to display data within the range of the selected relative date slicer. This would prevent users from inadvertently selecting a date range that is too large and causing the report to slow down or crash. If you have access to the report's design, you may be able to modify this behavior by adjusting the report's settings or editing the code. Otherwise, you may need to contact the report's creator for further assistance.
Best Regards