Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
I know direct query in power bi doesn't allow calculated tables as that blocks automatic refresh.
Are power bi parameters defined something like this cause any problems with refresh?:
Table1 and Table2 are both queried using DirectQuery in report.
I noticed the symbol for parameter and calculated table on data tab seems to be the same.
Measures = {
("Measure1", NAMEOF('Table1'[Measure1]), 0),
("Measure2", NAMEOF('Table2'[Measure2]), 1)
}
Solved! Go to Solution.
@afaro , Parameter table, and Calculated table are both import modes. So should be fine. Juts check the Table type in Model View.
Hi @afaro ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hello @afaro ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @afaro ,
Thank you for reaching out to the Microsoft Fabric Community. Also thank you @amitchandak and @TomOs for your inputs.
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Using Power BI parameters with DirectQuery mode does not inherently block refresh, but there are some caveats. Unlike calculated tables, which generate static data at load time, parameters act as dynamic inputs and are usually resolved at query execution, making them more flexible
However, issues can arise if the parameters influence calculated tables or columns, as those require import mode or static evaluation. Also, if parameters are used to dynamically filter DirectQuery sources in ways that create complex query dependencies, you might run into performance or refresh issues
The icon similarity between parameters and calculated tables in the data tab is just a UI design choice and doesn't indicate the same behavior. If you're seeing refresh problems, check if your parameters indirectly reference computed elements that require Import mode.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 69 | |
| 63 | |
| 32 | |
| 31 | |
| 25 |