mdebeleFrequent Visitor10 years agoStatus: AbandonedCannot edit, update, content packs. Generating error Something went wrong. Failed to publish Organizational Apps Please try again later or cNULL
3 CommentsReplies sorted by Most LikedchassImpactful Individual6 years agoHello, Looks like your error was cut off can you please finish the description? chassImpactful Individual6 years agoHello, I will close this issue until we get the complete error..hope that is okayfbcideas_migusrNew Member1 year agoStatus added: Abandoned
chassImpactful Individual6 years agoHello, Looks like your error was cut off can you please finish the description?
chassImpactful Individual6 years agoHello, I will close this issue until we get the complete error..hope that is okay
Recent ideasAll Idea StatusesNewNeed ClarificationNeeds VotesUnder ReviewPlannedCompletedAbandonedTagged:TagMost RecentEnable Analyze in Excel / live connection for external (cross-tenant) users Enable Analyze in Excel / live connection for external (cross-tenant) users 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 ...Make 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...Support 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...Auto-propagate Lakehouse (Direct Lake) permissions to users assigned to a Power BI App audience Problem When a Power BI report uses a Live Connection to a Direct Lake Semantic Model, end users must have explicit ReadAll / ReadData permissions on the underlying Lakehouse (or its SQL analytics e...
