Forum Discussion

BSLATTER's avatar
BSLATTER
Icon for Helper III rankHelper III
5 years ago
Solved

Power BI Goals - No data in dataset

I am attempting to POC the new Power BI goals feature. I've set up a new scorecard, added some measures (some manual, some automated) and am now trying to connect to the backend dataste in the Power ...
Need Help
  • justynalucznik's avatar
    justynalucznik
    5 years ago

    Hi BSLATTER ,

     

    We had a limtiation when we first released that the dataset was not available. Unfortunately we could not fix this for existing scorecards. Could you please try creating a new scorecard, adding a new goal and taking a look if the issue is resolved? If it still isn't working I'll get our engineers to take a look. Sorry about the inconvenience!

     

    Justyna

V-lianl-msft's avatar
V-lianl-msft
Icon for Community Support rankCommunity Support
5 years ago

Hi BSLATTER ,

 

Here's the limitations-and-considerations for live connection to Power BI dataset.

https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-report-lifecycle-datasets#limitations...

Limitations and considerations

When using the Power BI service live connection, there are a few limitations and considerations to keep in mind.

  • Only users with Build permission for a dataset can connect to a published dataset using the Power BI service live connection.

  • Free users only see datasets in their My Workspace and in Premium-based workspaces.

  • Since this connection is a live connection, left-navigation and modeling are disabled. You can only connect to one dataset in each report. This behavior is similar to the behavior when connected to SQL Server Analysis Services.

  • Since this connection is a live connection, row-level security (RLS) and other such connection behaviors are enforced. This is the same as when connected to SQL Server Analysis Services.

  • If the owner modifies the original shared .pbix file, the dataset and report that is shared in the Power BI service is overwritten. Reports based on that dataset aren't overwritten, but any changes to the dataset are reflected in the report.

  • Members of a workspace can't replace the originally shared report. Attempts to do so result in a warning that prompts you to rename the file, and publish.

  • If you delete the shared dataset in the Power BI service, then other reports based on that dataset will no longer work properly or display their visuals.

  • For Content Packs, you must first create a copy of a content pack before using it as a basis for sharing a .pbix report and dataset to the Power BI service.

  • For Content Packs from My Organization, once copied, you can't replace the report created on the service or a report created as part of copying a Content Pack with a live connection. Attempts to do so result in a warning that prompts you to rename the file, and publish. In this situation, you can only replace published live connected reports.

  • Deleting a shared dataset in the Power BI service means no one can access that dataset any longer from Power BI Desktop.

  • Reports that share a dataset on the Power BI service don't support automated deployments using the Power BI REST API.

I did some test but didn't find any problem. By the way, What is your role in the workspace? If you are a viewer, do you have build permission on the dataset?

 

Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.