Forum Discussion
Error message when trying to prep model for AI
Hi TerYeah,
Thank you for the update.
Based on our understanding, the error “NullSchemaPackageEvenAfterForcedUpdate” might occur when Power BI fails to generate the Copilot AI schema package for a specific semantic model during the “Simplify data schema” process. The issue might be caused by the size or metadata complexity of the model rather than an environmental problem. Additionally, the Prep data for AI button being disabled in Desktop may be due to your report using a Live Connection. In this architecture, the semantic model metadata can only be edited in the Service, not in Desktop.
Also, Copilot might rely on a simplified semantic model schema and recommends reducing schema complexity to improve grounding and packaging reliability. As a workaround, open the semantic model directly in the Power BI Service, go to Prep data for AI and select Simplify data schema, manually deselect most tables and fields, keeping only 1 to 2 primary fact tables and a small set of key measures. Apply the changes. This controlled reduction might allow the AI schema package to generate successfully.
If the issue persists even after schema simplification, we kindly request you to raise a support ticket using the provided link:Microsoft Fabric Support and Status | Microsoft Fabric so that the backend team can analyse the issue.
Additionally, please refer to the links below:
Prepare Your Data for AI - Power BI | Microsoft Learn
Enable Fabric Copilot for Power BI - Power BI | Microsoft Learn
Copilot in Power BI tutorial - Prepare semantic model for AI - Power BI | Microsoft Learn
Best practices to optimize Q&A - Power BI | Microsoft Learn
Overview of Copilot for Power BI - Power BI | Microsoft Learn
We hope the information provided helps to resolve the issue. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.
Thank you.
Thanks, but like I said, "Prep for AI" is disabled in PBI Desktop, so the only place it's available to me is from the service. So obviously, I've already tried that "workaround". And as stated previously, when trying to select "Simplify data schema" I never get to the actual dialogue, it spins for 90 seconds before giving the error message.