Forum Discussion

Russo's avatar
Russo
Icon for Helper I rankHelper I
7 months ago
Solved

artifact is missing connection details

I have a new report that I'm pulling data from a semantic model from another report that I own also. (one table only).  All is well but when I published it..  it's getting an error from the published...
Need Help
  • v-karpurapud's avatar
    v-karpurapud
    7 months ago

    Hi Russo 

    Thank you for reviewing all the steps and confirming the permissions and credentials. Since Build access is set correctly on the semantic model, credentials have been revalidated, and the report has been republished, but the issue persists only in Power BI Service, it suggests a Service-side binding problem or an unsupported scenario with thin reports rather than a misconfiguration. At this point, there aren’t any further permissions or settings to change, and local troubleshooting is unlikely to help. For a clear resolution, opening a Microsoft support ticket using 

    Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn would allow them to check the dataset and report IDs on the backend. Alternatively, switching from the semantic model connection to importing the table or keeping the dataset and report in the same workspace could be a practical solution.


    If you have any further questions, feel free to reach out and we'll be glad to assist.
     

    Regards,

    Microsoft Fabric Community Support Team.
     

Anonymous's avatar
Anonymous
Not applicable
7 months ago

Hi Russo ,

Thank you for confirming and sharing the screenshot.

Here are a few key steps to help narrow down the issue:

  1. Check that Build permission is granted on the semantic model itself (Dataset → Manage permissions), not just on the report or workspace.
  2. Make sure the permission is assigned to the same user account accessing the report in Power BI Service, and not to a different tenant or a cached sign-in.
  3. Once Build is granted, open the report in Power BI Desktop, refresh the model connection, and republish the report to Service. Sometimes, published reports keep outdated connection metadata.

Permission changes are usually applied quickly, but republishing may be necessary for Service to recognize the updated connection.

If the issue remains after these steps, please let us know.

 

Thank you.

  • Russo's avatar
    Russo
    Icon for Helper I rankHelper I
    7 months ago

    Hi Anonymous  the picture that I showed was of the semantic model.. so it does have build permission granted.  It's the same on both models also.