Getting an error on a visual saying data cannot be retrieved when published
Hi all, I just published a Power BI dashboard to a workspace, and I am getting an error on one of the visuals saying that it cannot retrieve the data. The dataset is currently blank (it tracks live data and there is no data for that specific table today). Am I getting an error because the data is blank, or can it actually not communicate with the source? All other visuals from the same database appear fine.
Power BI: Displaying Anonymous Competitor Data with Store-Specific Filters on SharePoint
The situation I'm grappling with is as follows: I've designed a dashboard for a client that displays data from 150 distinct stores. These stores are owned by 55 individuals, with some of them having ownership over multiple stores. The dashboard I developed showcases Key Performance Indicators (KPIs) for each store and contrasts them with the 6 most comparable stores based on 2023 revenue. Users can select a specific store using a slicer to view its data alongside anonymized data of comparable stores. The intention is for owners to cycle through their stores using this slicer without accessing competitors' specific data. While they'll see metrics from competing stores if they're part of the comparison group, the information remains anonymous, ensuring they can't identify which stores they're looking at. I plan to deploy this report on SharePoint. Each owner accesses the report through their unique SharePoint URL, logging in to view the Power BI report tailored to their owned stores. The challenge lies in how to best implement this. Using Row-Level Security (RLS) doesn't seem fitting. This is because it would filter out all rows unrelated to the owner's stores, leading to visuals about comparable stores being devoid of data, as competitor data would be excluded at the row level. I've considered two potential solutions: Deploying 55 separate reports to the Power BI service, one tailored to each owner. The clear drawback is the considerable effort, especially if adjustments are needed later. Cloning the data model. Here, RLS would be applied to one, while the other remains RLS-free for comparison visuals. The downside is that it doubles the data model's size, leading to a notable dip in performance. Neither solution feels optimal, which prompts me to explore alternative approaches.
Disable/Prevent/Restrict/Block publish to cloud service for Power BI Report Server implementations
Our organization has implemented Power BI on-premise using Power BI Report Server (SA), however we have run into a key blocking issue which is currently preventing us from going live across our organization. Due to our company’s policies, we need to block our users from being able to publish to the cloud service. We only want our users to publish to the on-premise PBI Report Server. However, the licensing model for an on-premise implementation requires that ‘publishers’ (users who want to publish to the on-premise Power BI Report Server) must have a Power BI Pro license. We have procured PBI Pro licenses for our publishers, however this license also enables them to publish to the cloud service as well without any restrictions or controls. For our organization, this is considered a significant risk and we need to disable cloud publishing. Disablement of cloud publishing would seem to go hand-in-hand with an on-premise implementation utilizing Power BI Report Server since most organizations are choosing this implementation route to avoid storing their data in the cloud. This is further complicated since we are a U.S. subsidiary of a global enterprise in which the O365/Power BI cloud region has been set to store our data in the E.U. We are looking for help and guidance for how to configure our Power BI on-premise implementation and/or PBI cloud service to disallow our users the ability to publish to the cloud service; which is administered by our parent and utilized by multiple subsidiaries. We have spent much time researching and applying various configurations without success.
Unable to publish report to RS (September 2021 Version)
PowerBi Report Server version Version 1.12.7936.39665(September 2021) running on Windows Server 2016 SQL server 2016 PowerBi Desktop Version: 2.97.863.0 64-bit (September 2021) Save as via PowerBi Desktop RS, "An error occurred while attempting to save the repot to PowerBI Report Server." Upload via Report Server: "There was an error uploading your .pbix file. Verify that the file has not been corrupted and that the file extension matches the format of the file." Error from the RSPortal log: |ERROR|92|library|Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item 'xxx.pbix’ cannot be found.; |ERROR|93|The remote server returned an error: (400) Bad Request. Error from the RSPowerBI log: |ERROR|8|HttpRequestContext returned false for IsLocal. The PowerBI RS service is running under a domain account which is local admin. Also tried the default accounts some issue. Can create folders on the site. I've seen this error mentioned but none of the suggestions so far have helped. Anyone resolved this error for September 2021 version?Best way to control different levels of access to a dashboard
Hi All, I have built a report for a client that will have multiple users, each of these users will have access to differing levels of security and therefore should only be allowed to see the dashboard tabs that relate to their level of access. Is it possible to publish the same pbix file multiple times granting different access each time? If not, can I save multiple versions of the PBIX file and just publish them to the different workspaces like that? What is best practice here? Thanks so much.Sharing dashboard outside my organization
Hello everyone, I am working with Power BI to create a dashboard to be shared with my client, but my company does not allow sharing plublished dashboards with employees outside the organization, so I was wondering if anyone faced the same problem and has a solution to bypass it. Thanks! Jorge