Forum Discussion
Semantic Model: Error on refresh and not gracefully
- 1 year ago
Update on this. We have implemented a solution that is working for anyone else struggling with this.
With the help of some very talented engineers, we impletmented a custom dbt materialization method that no longer drops and creates tables on refresh. Ever since that change, we haven't had any errors with the semantic model refresh.
This adds to the suspision that fabric has some bugs with how it handles the parque file relationships.
I'll mark this as the solution. Happy coding everyone.
Hi NoDice ,
I would also take a moment to thank ryan-schofield , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
Unfortunately, there’s currently no programmatic equivalent to the Edit Tables refresh in the Semantic Model UI, so the only consistent fix others have found is:
- Drop and recreate the table.
- Manually refresh the semantic model via Edit Tables.
Because this behavior is a long-standing bug in Direct Lake mode and there’s no public workaround to programmatically re-bind the schema, I’d recommend to raise Microsoft Support ticket.
Please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Community Support Team
Hi NoDice ,
We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community.
Thank you.
- NoDice1 year ago
Advocate II
Following up once again? I'm confused. No, this isn't resolved.
- v-menakakota1 year ago
Community Support
Hi NoDice ,
Thank you for the reply, I understand this is still unresolved and frustrating.
May I ask if you’ve had a chance to open a Microsoft Support ticket for this issue?
Thank you.