Error pulling data form another semantic model

[masplin]

I have 2 semantic models and one is pulling some data from the other including just the refresh time.

It seemed ot be working fine just pulling in a table of data, but I just added the refresh time and getting this error just where the refresh date is displayed?  I'm not getting any error for the other data being pulled from the other model 

Underlying Error: OnPremiseServiceException
Activity ID: 07d03594-b96f-48b8-b397-20f2d2940ad8
Correlation ID: 3c53e663-b2e4-075a-2f06-2923fd3d9171
Request ID: 3c7ab2e8-b6bf-44c1-831b-03490299a92e
Time: Fri May 29 2026 10:12:21 GMT+0100 (British Summer Time)
Service version: 13.0.28503.502
Client version: 2605.4.29440-train
Cluster URI: https://wabi-uk-south-b-primary-redirect.analysis.windows.net/

Any clues what this means? the pbix works fine no issues. 

[krishnakanth240]

Hi @masplin 

Can you try republishing both models, refreshing credentials or gateway mappings, and replacing refresh time logic with a calculated table or measure instead of metadata / DMV based queries. Also test with simple measure from the source model to confirm cross model connection itself is working

[Poojara_D12]

Hi @masplin 

I think this OnPremiseServiceException error happens because your second semantic model is configured with a local timezone format (like British Summer Time) that conflicts with the strict cloud format requirements when passed between chained datasets. When you pull a dynamic refresh timestamp locally in Power BI Desktop, the engine handles the data type flexibly, but once published, the Power BI Service requires datetime strings coming from a cross-dataset query to be explicitly locked down to an absolute ISO standard or UTC format to prevent the backend gateway layer from crashing.

To fix this, go back into your first semantic model's Power Query editor where the refresh time is generated, and explicitly convert that timestamp column to text or force it to UTC using DateTimeZone.ToUtc(DateTimeZone.LocalNow()). If you convert it to a plain text string before passing it to the second model, it completely bypasses the cloud timezone validation check, which will resolve the error instantly on the Service without breaking any of your other cross-model table links.

[Mauro89]

Hi @masplin,

at least the error message states something regarding "onpremiseservice". I would check the following:

1. In semantic model settings, re-check Gateway and cloud connections and re-enter credentials for every source.
2. Confirm users of the connection or semantic model have required Read/Build permissions on all semantic models in the chain.
3. Check Refresh history and gateway logs for the same timestamp

Hope this helps to troubleshoot.

Best regards!