User Profile
prasadpatil020
Helper I
Joined 9 months ago
User Widgets
Contributions
Re: OLS Access Conflict: PII vs Non-PII Access in Power BI
Hi ShahRukhSameer , Thanks for the suggestion. We will convey this to the Access Management team. If they are able to implement it, that would be ideal. Otherwise, we will need to explore alternative approaches or educate users and managers that a user can only have one type of access at a time, either PII or Non-PII, but not both. We are considering the following approach: Display a clear message during the access request process stating that a user can request either PII access or Non-PII access, but not both. If a user already has PII or Non-PII access and attempts to request the other access type, the portal should automatically reject the request and display a message such as: "You already have an existing access type assigned. Users can hold only one access type (PII or Non-PII) at a time. If you require a different access type, please remove your current access and then submit a new request." Before approving a request, managers should be able to view: The user's current access. The newly requested access. A warning message when the requested access conflicts with the user's existing access. Based on this information, managers can make an informed decision on whether to approve or reject the request.73Views3likes1CommentRe: OLS Access Conflict: PII vs Non-PII Access in Power BI
Hi ShahRukhSameer , Thanks for the detailed information. As you mentioned: "If PII access is approved, move the user from the Non-PII group to the PII group rather than adding them to both." Could you please suggest the best approach to achieve this?83Views1like3CommentsRe: OLS Access Conflict: PII vs Non-PII Access in Power BI
Hi GeraldGEmerick , Thank you for the suggestion. However, we cannot add all the PII columns into a single table, as this would not align with the business logic. The columns are categorized based on different domains such as customer details, delivery details, service details, order details, and others. Therefore, consolidating all PII-related columns into a single table is not feasible.100Views0likes1CommentOLS Access Conflict: PII vs Non-PII Access in Power BI
Hi Community, Hope you are doing well. I have a question regarding Object-Level Security (OLS) in Power BI. We have two access types: PII Access: Users can view all data in the report, including sensitive PII columns. Non-PII Access: Users can view the report, but certain sensitive user information columns are restricted through OLS. Access is managed through Azure AD groups, and users can request access via our internal access management process. Current Challenge The issue occurs when a user requests both PII and Non-PII access, and both requests are approved by their manager. When a user becomes a member of both access groups, they are unable to view the report data correctly. Based on our understanding, this appears to be related to the behavior of OLS when a user belongs to roles with conflicting object permissions. What We Are Trying to Understand We are evaluating whether there is any supported approach where: A user can belong to both PII and Non-PII access groups. The report continues to work correctly. Data security is not compromised. However, we have concerns about the security implications. For example: A user initially has Non-PII access, meaning they are not allowed to view sensitive PII information. The same user later requests PII access, and the request is approved. The user now belongs to both groups. If we implement a solution that allows users with both access types to see all data, it could potentially expose PII information to users who were originally assigned a Non-PII access model, which may violate our data security requirements. Questions How does OLS behave when a user belongs to multiple roles with conflicting permissions? Is it technically possible and supported to have both PII and Non-PII access assigned to the same user? If so, what is the recommended design pattern to handle this scenario? If not, is the recommended approach to enforce a business rule that a user can have either PII access or Non-PII access, but not both simultaneously? Any guidance, best practices, or real-world experiences would be greatly appreciated. Thanks in advance!Solved158Views0likes9CommentsHow to create tooltip for card visuals
Hi Community..!! I have five Card visuals on a single report page in Power BI. When a user hovers over each Card, I want to show some descriptive / explanatory text, and the text should be different for each Card. I do not want to create different pages for tooltip for each card visual. How can we build this. Thanks in advance..!!Solved413Views0likes4Commentsincremental refresh policy
Hi Community..!! I am using incremental refresh in the power bi , 1 year data and incremental refresh on 2 days on updated date, we have kept refresh twice a day in power bi workspace, but report is not showing correct order status, if we keep incremental refresh on 3 months on updated date then order status are getting correct but not on 2 days refresh. what will be the issue? does keeping two days on updated date will not work? how the incremental refresh works on updated date? why the data is wrong? Could anyone please help me on this? I am attaching screenshot for your reference. Thanks in advance..!!805Views1like9CommentsPower BI Service → Workspace → Refresh history ->Refresh Duration
Currently, in the Power BI Service → Workspace → Refresh history, we can see the following columns: Details Type Start (Date & Time) End (Date & Time) Status Message However, there is no column that shows how long the refresh actually took. Requested Enhancement Add a new column called “Refresh Duration” that automatically calculates the difference between Start and End date/time and displays the total refresh time (for example: 42 minutes 58 seconds or 00:42:58). Why this is useful Helps quickly identify long-running refreshes without manual calculation Makes it easier to compare performance between refreshes Useful for capacity monitoring, troubleshooting, and optimization Improves visibility for admins and report owners, especially when dealing with multiple datasets Current Challenge Right now, users must manually subtract the Start and End times or export the data elsewhere to calculate refresh duration, which is inefficient for routine monitoring. Expected Benefit This enhancement would improve usability and provide immediate insights into refresh performance directly within the Power BI Service UI. Thanks, Prasad Patil94Views0likes0Comments
Data Privacy
Microsoft Fabric Community and Privacy
To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.