Login

u/mrbartuss

r/PowerBI r/MicrosoftFabric
How do you handle schema refreshes for Import models?
▲ 3 r/MicrosoftFabric+1 crossposts

How do you handle schema refreshes for Import models?

I have an Import mode model pulling from a Lakehouse SQL Analytics Endpoint, and a new column was recently added upstream.

According to the official documentation, "Changes in data source table structure, or schema, such as a new, renamed, or removed column can only be applied in Power BI Desktop."

Because of this limitation, I currently have to manually open the .pbix in Desktop, refresh to pull the new column, and republish.

How are you all automating this in production so you don't have to open Desktop?

  • Can this be done easily with Tabular Editor via CLI or other means?
  • Has anyone used semantic-link-labs to force a schema sync for Import mode?
  • Are there any other tricks you use to handle schema drift?
u/mrbartuss — 3 days ago
▲ 7 r/MicrosoftFabric

Fabric quirks: Timezone format mismatches and fake circular dependencies?

Hi everyone, I'm hitting two weird validation issues in Fabric pipelines and just wondering if anyone knows why it behaves like this.

1. Timezone preview vs. pipeline run

I'm using the convertTimeZone function.

  • If I use a standard timezone like 'Europe/Warsaw', the "Evaluate expression" preview works fine, but the actual pipeline run fails.

https://preview.redd.it/pmv0sa1q575h1.png?width=1451&format=png&auto=webp&s=f284f5eb1b120837c5f8ebe2ab7c3b956b6fd8aa

https://preview.redd.it/tfbyq0cy575h1.png?width=595&format=png&auto=webp&s=50da916fd5ca813d9a8b54b969d3e56b39613a4f

  • If I use a Windows timezone like 'Central European Standard Time', the UI preview throws an error, but the actual pipeline run succeeds. Why do the frontend preview and the backend run require two completely different timezone formats?

https://preview.redd.it/1dyfc3ak575h1.png?width=1426&format=png&auto=webp&s=9429882184a45933682a8c8ae1a0db20b16e5a43

2. Fake circular dependency with dynamic IDs

I use library variables to pass pipeline IDs dynamically (e.g., @pipeline().libraryVariables.MyPipelineId`) so my CI/CD deployments work across environments. However, whenever I use a dynamic ID in an "Invoke Pipeline" activity, Fabric refuses to validate it cleanly and throws this error:

Circular dependency found with pipelines... Please review your dependency path

It seems I am not alone:

* Interesting Behaviour Dynamic Pipeline Execution : r/MicrosoftFabric

* https://www.reddit.com/r/MicrosoftFabric/comments/1q5mte6/question_about_variable_libraries_and_pipelines/

How are you handling dynamic pipeline IDs for CI/CD without breaking the validation engine? Are there actual technical reasons for this, or just UI bugs?

reddit.com
u/mrbartuss — 1 month ago
▲ 22 r/PowerBI

What happened to the May 2026 Feature Summary?

https://community.fabric.microsoft.com/t5/Power-BI-Updates-Blog/bg-p/fbc_pbiupdatesblog#_Toc229397343

The new May feature summary was released, but now it's completely deleted.

There's a lot of bragging on LinkedIn right now about the new GA functions, but there's no actual May version available anywhere.

  • The official Power BI download page is still on the old version.
  • It's not in the Microsoft Store either.

Did Microsoft pull the update at the last minute due to a bug?

u/mrbartuss — 2 months ago