Forum Discussion

Russo's avatar
Russo
Icon for Helper I rankHelper I
8 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 ,

 

Since Build permission is already set on the semantic model and the screenshot shows this, the problem is likely due to a stale or incomplete connection reference in the thin report. This can occur when the report uses cached metadata from before permissions or credentials were updated.

While the report may work in Desktop, Power BI Service depends on the semantic model’s connection settings and valid credentials. Make sure the semantic model has valid data source credentials in the Service, then open the thin report in Power BI Desktop, reconnect to the semantic model (or rebuild the visual), and republish the report. Republishing usually refreshes the artifact metadata and resolves the artifact is missing connection details error when Build is already granted.

 

Thank you.