artifact is missing connection details

[Russo]

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 version report:

 I've revalidated my data source credentials in both reports.  I'm also using Oauth2 and Public, which I always use.  Is there a data share permission setting that i'm missing somewhere to toggle?  or any help in general for how to resolve this issue. 

This error is causing one of my visuals within my report to not show up.. and  yes it happens to be using on the same table that I'm pulling data from the other PBI report. 

[v-karpurapud]

Hi @Russo 

We wanted to follow up and ask if you have submitted a support ticket. Could you let us know if the issue was resolved after creating the support case?If you have any further questions, please let us know. we can assist you further.

Regards,

Microsoft Fabric Community Support Team.

[Russo]

I have moved on to other priorities and will not be submitting a ticket at this time.  I will be revisiting this months down the road and if I get the same error message I will submit a ticket.  I choose not to use the semantic model connection at this time.  Thank you for the follow up. 

[v-karpurapud]

Hi @Russo 

Thank you for the update. If you have any more questions, please let us know and we’ll be happy to help.

Regards,

Microsoft Fabric Community Support Team

[Anonymous]

Hi @Russo ,

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.

Thank you.

[Russo]

Hi @Anonymous yes and thank you for the suggestions.. great suggestinos, I tried them both and unfortunately still not working.  I'm leaning towards cutting my losses here and not using semantic model connection.

[v-karpurapud · Accepted solution]

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]

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.

[Anonymous]

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]

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. 

[cengizhanarslan]

Owning the report is not enough.

Go to the source dataset (semantic model) → Manage permissions and ensure:

• Your user (or a security group) has Build permission

Without Build:

• Desktop can still query (cached credentials)

• Service visuals fail with artifact missing connection details

[Russo]

It's still not working.. I have added myself as build permission.. unless im misunderstanding your instructions, please let me know.  Any other thoughts?  or does this take a while to update?