Forum Discussion
Error pulling data form another semantic model
Hi masplin ,
As a next step, could you please perform the following test?
Create a new report page in Model 2.
Add a table visual containing only a simple text column from Model 1.
If possible, temporarily remove or disable any calculation groups that may be impacting the query.
Republish the report and verify whether the issue persists in the Power BI Service.If the same error occurs with a basic text column and no calculation group involvement, this would help confirm that the issue is not related to the refresh date logic itself but rather to the cross-semantic model query execution.
In that case, we would recommend opening a Microsoft Support ticket and providing the Activity ID, Correlation ID, Request ID, and timestamp from the error message. These details can be used to review the backend logs and identify the exact point of failure during query execution.
Please let us know the results of the above test, and we'll be happy to continue investigating.
Thank you.
Hi masplin ,
Thank you for the detailed investigation and for sharing your findings.
Based on the behavior you've described, this does not appear to be related to the refresh date value or its data type. The key observation is that fields originating directly from Model 1 work in a standalone report but generate an error when referenced directly within Model 2, while the same values function correctly after being materialized into a local column in Model 2.
To help narrow down the root cause, could you please confirm the following:
Do both semantic models reside in the same workspace and capacity?
Is Model 2 configured as a composite model using DirectQuery to Model 1?
If you add a simple text column from Model 1 directly to a table visual in Model 2, does the same error occur?
Additionally, please verify the following:
The semantic model owner and report consumers have both Read and Build permissions on Model 1.
DirectQuery for Power BI semantic models and Analysis Services is enabled and supported within your tenant.
The source semantic model does not contain features that may impact composite model scenarios, such as RLS, calculation groups, or other unsupported configurations.
Whether the issue can be reproduced consistently, and if so, capture a browser trace (F12) alongside the Activity ID and Correlation ID for further analysis.
Given that a blank PBIX connected directly to Model 1 works as expected, the current evidence suggests the issue may be occurring during query execution across the chained semantic model relationship rather than with the underlying data itself.
Please let us know the answers to the questions above, and we'll be happy to investigate further.
Both models in the same workspace and we dont have any premium capacity
Model 2 has its own sources mostly Microsoft Dynamics CRM and some excel sheets on Sharepoint. It is using directquery for one comparison table on model 1
Yes if I try to drop a column from the connect Model 1 table into a visual in Model 2 it errors when published, but not in the pbix
I am the owner of both models
The directquery is working in that I can use the data from Model 1 in the origanl table I added. So I assume its enabled
Model 1 & 2 both contain calculation groups
I dont know what this means "Whether the issue can be reproduced consistently, and if so, capture a browser trace (F12) alongside the Activity ID and Correlation ID for further analysis.". The error is consistent for any direct use of Model 1 connected tables
Thanks
