Forum Discussion
Forced Schematic Model
Kedar_Pande - Actually this is NOT expected behavior. If a report and paginated report are connected to the same model, when publishing you should not / will not get a seperate schmatic model.
There is a glitch/bug where actually ALL of my report were failing to publish and if I deleted them and published, then I would get a new schmatic model despite them already being connected to one.
The solution was simply to reconnect/refresh the report to the datasource model. Once I did this, and published the report with the embedded paginated report, I didn't get a new schematic model after publishing.
Yes, this behavior is expected. When you embed a paginated report into a Power BI report, Power BI generates a new dataset model (or schematic model) specifically for that embedded paginated report. This is because paginated reports and standard Power BI reports typically operate on separate data models, and the system creates a distinct model to handle the paginated report's requirements.
💌 If this helped, a Kudos 👍 or Solution mark would be great! 🎉
Cheers,
Kedar
Connect on LinkedIn
Thanks Kedar_Pande - I was hoping not but makes sense. I guess I will link the report to app as a menu item then. I want to keep my models to a minimum. Best wishes.
Kedar_Pande - Actually this is NOT expected behavior. If a report and paginated report are connected to the same model, when publishing you should not / will not get a seperate schmatic model.
There is a glitch/bug where actually ALL of my report were failing to publish and if I deleted them and published, then I would get a new schmatic model despite them already being connected to one.
The solution was simply to reconnect/refresh the report to the datasource model. Once I did this, and published the report with the embedded paginated report, I didn't get a new schematic model after publishing.