Anonymous
My feedback
-
79 votesAnonymous
supported this idea
·
-
612 votesAnonymous
supported this idea
·
-
2,414 votes
This is in our backlog. Stay tuned for more updates!
Anonymous
supported this idea
·
-
3,674 votes
This is on our roadmap but we don’t have a specific timeline to share at this point. We’ll update this when we have more details!
Anonymous
supported this idea
·
-
71 votesAnonymous
supported this idea
·
-
5,404 votes
Thanks for the feedback! While this isn’t (yet!) on our near term roadmap, please keep voting and giving us feedback on the idea. We definitely see the need and will update the idea when we are closer to adding this feature.
Anonymous
commented
As others have said this should be prioritised, it's one of those features that you expect to be there. Not having it makes it seem like a poor tool to the average user.
Additionally having it work at lower levels just makes the tables look strange. Most will be using this to highlight key information, in my case it's used to highlight positive and negative variances. Users can see at a glance if they're over or under budget at a monthly level but at the total level they need to look at the numbers and do a mental calculation (Income and expenditure are displayed as positive and negative respectively, so a negative variance doesn't always mean it's bad). The quicker a user can interpret data they can see the better and we should be able to do all we can to aid this. Visuals are supposed to communicate.
Anonymous
supported this idea
·
-
1,860 votes
This month we added the ability to format text fields based off a numeric field: https://powerbi.microsoft.com/en-us/blog/power-bi-desktop-may-2018-feature-summary/#conditionalFormatting
We also are planning on adding a feature that will let you format your text based on comparisons. I’ll update this idea based on our progress on that feature.
Anonymous
commented
It would be great if the expansion of this feature allowed for DAX statements as this would really open up the functionality
Anonymous
supported this idea
·
-
1,400 votesAnonymous
supported this idea
·
-
1,136 votesAnonymous
supported this idea
·
-
259 votesAnonymous
supported this idea
·
-
425 votesAnonymous
supported this idea
·
-
4,692 votesAnonymous
supported this idea
·
-
4,301 votes
Checking with Will Thompson and moving status to backlog
Anonymous
supported this idea
·
-
48 votesAnonymous
supported this idea
·
Anonymous
commented
I agree with this, I'm sure many have had to disable this feature as there is no way to control who can see what. I'm having to integrate power apps at the moment to have a commenting system that respects security settings however this means users don't benefit from handy features like automatic bookmarking.
If RLS is too difficult to implement at this level (I understand why) then having the ability to lock visibility to the poster of the comment and whomever they have tagged with an @ is the next best thing.
This shouldn't affect what the owner of the report and those given full access can see however.
I think this should be prioritised if it's a viable feature as security was one of the most mentioned issues with commenting even back when it was first introduced for dashboards. At report level it is even more important to have some level of control over who can see what.
-
381 votesAnonymous
supported this idea
·
I agree with this and it is urgently needed. It doesn't make sense to limit end users in this way especially as they previously had this function.
My organisation uses Power Bi for management accounts, giving users build access would be giving them access to sensitive information they shouldn't see.
"Export to excel" is one of the most basic features that all users would expect to be able to do. It's quite akward explaining that this function isn't available to them on a microsoft product.