We are attempting to deploy the semantic model from the Dev stage to the Test stage, but we are encountering an error stating that the dependent artifacts must be deployed first to the target stage. In our case, some of these dependent artifacts are in different workspaces and have different owners, which makes this requirement impractical in many scenarios.
If this restriction could be removed, it would make working with the deployment pipeline much easier.
No CommentsBe the first to comment
Recent ideas
Allow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara1 hour agoNew MemberNew16Views1like1CommentAllow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels8 hours agoAdvocate IIINew184Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen9 hours agoAdvocate INew298Views47likes2Comments