Hi,
we need to have possibility to control audiences by having more settings. If for same app we have more than one audience, by default every user is forwarded to 'ALL'. This is confusing for them. I know is obvious for developers and more advanced users, but for simple users or beginners is hard to understand.
I would offer
- Possibility to have multiple apps per workspace where you can control every app separately
- For audience please give more flexibility and possibility to forward user to accessible audience but not to default 'ALL'
4 Comments
- fbcideas_migusrNew MemberStatus added:New
- rob_carettaRegular VisitorI would like to request that the 1 app per workspace limitation be changed. This is a very constraining limitation. https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-create-distribute-apps#consider... Why not treat apps like other assets in a workspace, just like folders and reports. We have different combinations of reports for different audiences. Setting up different workspaces just for another app will create a lot of extra overhead. Understand there are audiences for the single app, but I don't think that design model scales well. I don't particularly like having different sets of permissions mixed up inside of a single app container. I would rather have multiple apps with the permissions surfaced up inside the workspace. Please see this forum thread for more information. https://community.fabric.microsoft.com/t5/Service/Enhancement-Request-Remove-Workspace-App-Limit
- dustinaskinpbiMicrosoft EmployeeStatus changed:NewtoCompleted
- dustinaskinpbiMicrosoft EmployeeStatus changed:CompletedtoCompleted
Recent ideas
Bulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal1401971 hour agoFrequent VisitorNew2Views0likes0CommentsAbout "Download SQL database project" and fix the downloaded project
1. The sqlproj must be fixed, it is downloaded without the xml markup line <?xml version="1.0" encoding="utf-8"> 2. The sdk must be updated: Actual: <Sdk Name="Microsoft.Build.Sql" Version="0.1...Jarrinf11 hours agoFrequent VisitorNew48Views3likes2CommentsEventstream MQTT broker source: V3.1.1 support
The Eventstream MQTT broker source supports connections with public MQTT brokers that offer MQTT V5 support. Please offer support for V3.1.1 too, because this is still a valid and widely used ver...svelde12 hours agoSuper UserCompleted1.4KViews6likes4Comments