Forum Discussion

artur4's avatar
artur4
Icon for Helper I rankHelper I
1 year ago
Solved

Issue when using direct live connection to existing sematic model

Hello,

 

I am trying to develop a power bi which uses two datasources: 1. Excel file, 2. Existing semantic model from another power bi.

When I add the live connection to the semantic model in power bi desktop, I can see the data and everything works. However, when I publish the report, I get the following error message:

 

I read in the forum to check the Data Source Credentials in the semantic model but it is greyed out in both the semantic models (the new one generated with the new report, and the old one where I am using the direct connection). I am the Admin.

 

Also, I am trying to import th data to remove the live connection, but I cannot; it's greyed out.

 

Anybody has the solution to this?

  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi artur4 

    Thanks SaiTejaTalasila Cookistador for your inputs.

    Power BI Desktop shows the data fine because it uses your local credentials. But once you publish to the Service, it relies on the credentials of the original semantic model. If you’re getting an error and the credentials option is greyed out, it usually means you’re not the owner of that dataset or don’t have enough access to manage its settings.

    Try opening the source semantic model directly in the Power BI Service. If you see a Take over option, click it. After that, go to Dataset settings > Data source credentials and update the credentials there.

    Thank you.

8 Replies

  • Hi artur4 

     

    Can you open the report using the semantic model? Do you see data or some errors message?

    I just want to check if the issue is comming  from the credentials or the live connection

    • artur4's avatar
      artur4
      Icon for Helper I rankHelper I

      Hello, 
      I can see the report with the semantic model. However, when I open it I get always the same message.
      It works only on Power Bi Desktop.

      • Cookistador's avatar
        Cookistador
        Icon for Super User rankSuper User

        ok, as you are not able to see the data in the source report, the issue is probably comming from the credentials

         

        What kind of datasource is it ? 

        can you take over the report before to try to edit the credentials in the source reports  ?

  • Hi artur4 ,

     

    What is your excel file location (local/one drive/SharePoint) ?

     

    Thanks,

    Sai Teja 

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi artur4 

    Thanks SaiTejaTalasila Cookistador for your inputs.

    Power BI Desktop shows the data fine because it uses your local credentials. But once you publish to the Service, it relies on the credentials of the original semantic model. If you’re getting an error and the credentials option is greyed out, it usually means you’re not the owner of that dataset or don’t have enough access to manage its settings.

    Try opening the source semantic model directly in the Power BI Service. If you see a Take over option, click it. After that, go to Dataset settings > Data source credentials and update the credentials there.

    Thank you.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi artur4 
    I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
    Thank you.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi artur4 
    I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
    Thank you.

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi artur4 

      Hope everything’s going smoothly on your end. We haven’t heard back from you, so I wanted to check if the issue got sorted. If yes, marking the solution would be awesome for others who might run into the same thing.