Forum Discussion
artifact is missing connection details
- 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.
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.
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-karpurapud7 months ago
Community Support
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.