Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

"Couldn't load the data for this visual" error with Composite Dataset in direct query mode

I have a report that connects to Dataset A and Dataset B in direct query mode. I do not have any other data sources in that report.

 

After publishing the report in a shared workspace (which is other than MyWorkspace), the report only works fine for the Owner group. 

 

But as soon as I share the report with end users, they see the following error in all the visuals. Any advice will be highly appreciated please.

 

Couldn't load the data for this visual

Couldn't retrieve the data for this visual. Please try again later.

Please try again later or contact support. If you contact support, please provide these details.

Hide details

  • Activity ID467f596e-e175-4faf-b445-9d1d2436930f
  • Request ID8c618bff-6e0b-f2da-4f88-cd7ae1a98033
  • Correlation ID1ee9de91-44f8-3874-b755-15c1be7af4df
  • TimeFri Jun 04 2021 08:41:05 GMT+0100 (British Summer Time)
  • Service version13.0.16120.55
  • Client version2105.3.06191-train
  • Cluster URIhttps://wabi-europe-north-b-redirect.analysis.windows.net/
  • aj1973's avatar
    aj1973
    5 years ago

    Hi Anonymous 

    I was about to reply and say that the users need to be members of the workspace or if the datasets are in separate workspaces then the users need to be also members of those 2 workspaces.

    Now, External users to consume your report means 2 solutions, Either you give them or add them as guests to your workspace with at least a Pro license or the workspace itself needs to move from shared capacity to premium capacity.

    Here is a link to Limitations

    https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-datasets-azure-analysis-services

     

     

     

10 Replies

  • aj1973's avatar
    aj1973
    Icon for Community Champion rankCommunity Champion

    Hi Anonymous 

    Not sure if by saying Dataset A and Dataset B you mean by Source A and Source B, because you can't build a single report from 2 datasets.

    Lets assume you meant by Source A and source B, in that case in Direct Query mode Data must come from a single source. So I am guessing that is the issue you are having.

     

     

    • Anonymous's avatar
      Anonymous
      Not applicable

      Thank you Amine for the quick response.

       

      These are the steps I did to create the report:

       

      1) I created Report A / Dataset A in import mode using various sources including third party APIs, SQL Database Tables, excel files etc. 

       

      2) I then created Report B / Dataset B in import mode separately. Both these reports are working fine in every way including the user access.

       

      3) I then enabled the preview feature namely "Direct Query for PBI datasets for PBI Datasets and AS as follows:

                  File -> Options and Settings -> Global Preview Features -> Direct Query for PBI Datasets and AS.

       

      4)  I then created report C in direct query mode that connects to Dataset A and Dataset B. This became possible after enabling the above preview feature. This report works fine in PBI desktop and even in the portal any users that belong to the owner workspace can see this report perfectly. 

       

      The error only shows up when users within the organisation who have been granted access to this report but are not members of the owner workspace try to access this report.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Just to add bit of further information. 

     

    In a normal report that is pulling data from one Power BI dataset in LIVE Connection mode, when the report is shared with end users the link works fine for them.

     

    But if the same report is upgraded to pull data from two Power BI dataset in DirectQuery mode then the link stops working for them. Further, when I add the end users as members in the workspace, it again starts working for them. 

     

    The problem is that we can't add all the users in our workspace. We are expecting some external users also to be consuming this report in near future.

    • aj1973's avatar
      aj1973
      Icon for Community Champion rankCommunity Champion

      Hi Anonymous 

      I was about to reply and say that the users need to be members of the workspace or if the datasets are in separate workspaces then the users need to be also members of those 2 workspaces.

      Now, External users to consume your report means 2 solutions, Either you give them or add them as guests to your workspace with at least a Pro license or the workspace itself needs to move from shared capacity to premium capacity.

      Here is a link to Limitations

      https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-datasets-azure-analysis-services

       

       

       

      • Anonymous's avatar
        Anonymous
        Not applicable

        Thank you Amine. Looks like you have well pointed out worspace upgrade. I think we haven't upgraded the workspace and hence are having to add memnbers to the workspaces. I already had the build access setup on the datasets in the chain though.

         

        I will give it a go and will update you here. I suspect it might take a bit of time as I will need to work with others to assess and implement this change. Once that has been fixed I will come back here and update you.

         

        Thank you again so much. 

  • Anonymous's avatar
    Anonymous
    Not applicable

    I am having the same or very similar problem. Very keep on finding a solution so please post any information you get here!

  • v-deddai1-msft's avatar
    v-deddai1-msft
    Icon for Community Support rankCommunity Support

    Hi Anonymous ,

     

    For app workspace, you can only grant build permission for Dataset A and Dataset B for users that you want to share the DQ report to .

     

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

     

    Best Regards,

    Dedmon Dai