Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
I’m new to Power Automate.
My Power BI report uses a live connection to SQL Server Analysis Services (SSAS).
I have a custom aggregated (calculated) table with three columns used for a Sankey chart.
Currently, the Amount column in the Sankey chart is calculated only for July 2025.
However, I want the Sankey chart to be responsive to the Date slicer in the report.
There’s currently no relationship between my Calendar table and the calculated table and won't be (because cal. table is formed with UNION, SELECTCOLUMNS, SUMMURIZE, ROW-just source, target and amount columns)
I plan to modify my DAX formula using SELECTEDVALUE() to make it dynamic.
My idea is to create a Power Automate flow that captures the user’s date selection, recalculates the DAX measure/table, and updates the chart.
Is this possible with Power Automate?
Can Power Automate send a parameter to Analysis Services?
Or should I instead write the table output to Excel or another data source to use it again for chart? And which license is needed for Power Automate and Power BI?
Thanks for your time beforehand!! I will highly appreciate it.
Solved! Go to Solution.
Thankyou, @Kedar_Pande and @DataNinja777 for your responses.
Hi Zarina_H,
We appreciate your enquiry through the Microsoft Fabric Community Forum.
Based on my understanding, calculated tables in Power BI are static and are evaluated only during model processing. They do not respond to slicers or user interactions. With a live SSAS connection, model changes such as recalculated tables are not supported, only measures can be dynamic.
Please consider the following approach, which may help resolve the issue:
Power Automate can be used for scheduled refreshes, dataset processing, or executing REST/XMLA API calls, but not for interactive slicer based recalculations. Use of the XMLA/REST API requires Power BI Premium or Power BI Premium Per User (PPU), and use of Power Automate with premium connectors requires a Power Automate Premium licence.
We hope the information provided helps to resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric Community.
Thank you.
Thankyou, @Kedar_Pande and @DataNinja777 for your responses.
Hi Zarina_H,
We appreciate your enquiry through the Microsoft Fabric Community Forum.
Based on my understanding, calculated tables in Power BI are static and are evaluated only during model processing. They do not respond to slicers or user interactions. With a live SSAS connection, model changes such as recalculated tables are not supported, only measures can be dynamic.
Please consider the following approach, which may help resolve the issue:
Power Automate can be used for scheduled refreshes, dataset processing, or executing REST/XMLA API calls, but not for interactive slicer based recalculations. Use of the XMLA/REST API requires Power BI Premium or Power BI Premium Per User (PPU), and use of Power Automate with premium connectors requires a Power Automate Premium licence.
We hope the information provided helps to resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric Community.
Thank you.
Hi @Zarina_H ,
As mentioned in the answer by Kedar_Pande below, use of a measure will solve your issue.
Measure used in chart will respond to your slicer selection as shown above.
I have attached a pbix file for your reference.
Best regards,
Rebuild your Sankey logic using measures instead of a calculated table. Measures respond dynamically to slicers.
The calculated table approach fundamentally can't work with slicers, it's a data model limitation.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 8 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |
| User | Count |
|---|---|
| 25 | |
| 16 | |
| 8 | |
| 7 | |
| 7 |