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 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 ...PeterDaniels4 hours agoAdvocate IIINew183Views0likes2CommentsMake 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...TeemuMultanen5 hours agoAdvocate INew293Views47likes2CommentsSupport Encrypted Sensitivity-Labeled Excel Files in Power Query
Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...ewarstdhyjugkhi5 hours agoMicrosoft EmployeeNew21Views6likes0Comments