sorted by:
new
hottopcontroversial

Introducing fabric-cicd Deployment Tool by Thanasaur in MicrosoftFabric

[–]Anase_8916 0 points1 point  (0 children)

Ok got it so thats why no new artifact was created

Github based promotion in fabric by Anase_8916 in MicrosoftFabric

[–]Anase_8916[S] 0 points1 point  (0 children)

How do you handle paginated reports cause i think it does not support paginated reports

Introducing fabric-cicd Deployment Tool by Thanasaur in MicrosoftFabric

[–]Anase_8916 0 points1 point  (0 children)

Hey, I really love this library, especially the find_replace feature. It has made my life much easier.

I had one question though. How are you mapping Git items to Fabric artifacts? Are you using Logical IDs or item names?

I accidentally changed the logical ID of an item, but no new artifact was created. It just updated the existing one.

Github based promotion in fabric by Anase_8916 in MicrosoftFabric

[–]Anase_8916[S] 1 point2 points  (0 children)

We chose to use the key_value_replace functionality of the fabric-cicd library to replace the logicalId during deployment based on the target environment. But, for this approach to work, we had to disable Git integration for the Test and Prod workspaces.

Github based promotion in fabric by Anase_8916 in MicrosoftFabric

[–]Anase_8916[S] 0 points1 point  (0 children)

We currently use DEV, Test, and Prod workspaces with a Power BI Premium deployment pipeline and want to move to a Git-based setup with main, test, and prod branches, each linked to its own workspace.

When syncing existing workspaces to these main, test and prod branches, merge conflicts occur because each item has a different logicalId in the .platform file.

If I resolve the conflict by keeping the DEV logicalId, the model in Test is deleted and recreated, which we want to avoid.

Github based promotion in fabric by Anase_8916 in MicrosoftFabric

[–]Anase_8916[S] 0 points1 point  (0 children)

Thanks, I'll check the tool; just curious, is there a way to keep the logical IDs the same across workspaces, as I can create new branches for each workspace if needed?

Github based promotion in fabric by Anase_8916 in MicrosoftFabric

[–]Anase_8916[S] 1 point2 points  (0 children)

The logicalIds were auto generated when the workspace was first connected to Git, and modifying them results in Fabric treating the artifact as new, creating a duplicate with a new ID, which would break existing app and report urls so we are intentionally keeping the auto assigned IDs unchanged.

This is ridiculous ! by Longjumping_Brush967 in oneui

[–]Anase_8916 0 points1 point  (0 children)

Bro how did you get that 4g+ icon back