Refresh not supported in Direct Query with Field Parameters

[muneeba]

Hi all,

I’m working on a Power BI dashboard using a DirectQuery semantic model. I’ve created two blank tables in the semantic model: one for measures and one for titles. In the dashboard-level PBIX file, I’ve defined my measures, then moved them to the blank tables to keep the model fully in DirectQuery mode and avoid a Mixed or Composite model.

To show dynamic column headers like “Premium 2025” and “Premium 2024” (based on current and last year), I used Field Parameters. This works fine in Desktop, but after publishing, the scheduled refresh fails, saying parameters in DirectQuery mode aren’t supported.

What I need:

• Dynamic column titles that update automatically each year (e.g. “Premium 2026” next year)

• Entire model must stay in DirectQuery

• A solution that allows scheduled refresh to work without errors

Any advice or workaround for this would be really helpful. Thanks in advance!

[v-sathmakuri]

Hi @muneeba ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @Akash_Varuna  for the prompt response.

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!!

[Akash_Varuna]

Hi @muneeba It might be because Field Parameters in DirectQuery mode are not fully supported for scheduled refresh, leading to errors post-publish. You could try replacing Field Parameters with calculated columns or measures that dynamically update based on the current year. Ensure these calculations are performed within the semantic model or use DAX expressions that are compatible with DirectQuery to maintain refresh functionality.

[muneeba]

The challenge is that I need measures displayed as columns in a Table, with dynamic column headers like "Premium 2025", "Premium 2024" based on current and previous year. As far as I know, calculated columns or measures alone can't create dynamic column names in a visual.

Is there any workaround to achieve this while keeping the model fully in DirectQuery?

Alternatively, would it make sense to move the measures and parameter table into the semantic model itself, so I can use a live connection in the dashboard PBIX instead of DirectQuery? Open to suggestions if there's a cleaner way.

[Akash_Varuna]

Dynamic column headers aren’t natively supported in DirectQuery, so you could use static placeholders ("Current Year" and "Previous Year") with dynamic content or tooltips to clarify the year. You could also look into custom visuals or paginated reports can handle this better. Moving measures and parameter tables to the semantic model allows switching to a live connection, fully supporting Field Parameters and eliminating refresh issues.

[muneeba · Accepted solution]

The only option I had in mind was to move all the measures into the Semantic Model.
To keep things organized and manageable, I used Folders within the model. Additionaly, I created Parameters in the Semantic Model to support dynamic filtering and logic. 

By doing this, we also enable a live connection, which allows real-time data refresh and interaction.

At this point, this seems to be the most practical and scalable solution.