Forum Discussion

Scalkins1743's avatar
Scalkins1743
Frequent Visitor
1 year ago
Solved

Report return error in visual after promotion in deployment pipeline, that is not seen in 1st stage

We are using deployment pipelines for promoting content developed in our [Test] workspaces. Our semantic models are kept in as separate workspace from our reports for workflow purposes so two separat...
Need Help
  • Scalkins1743's avatar
    Scalkins1743
    1 year ago

    Yes, we have had the issue resolved with Microsoft with the initiation of a manual refresh of the semantic model. This is even though the continuous sync is turned on for automatic updates through direct lake. 

     

    The explanation is that calculations do not automatically sync in the new workspace after deployment, so a manual refresh is necessary for them to display correctly. We're adding this to our deployment procedure to ensure this is done going forward.

Shahid12523's avatar
Shahid12523
Icon for Community Champion rankCommunity Champion
1 year ago

The 1,000,000 row error in QA happens because the promoted semantic model isn’t identical to Test — field parameters, relationships, or RLS are being applied differently, so queries return bigger resultsets.

 

Fix:
compare Test vs QA model in Tabular Editor/XMLA, check field parameters, RLS, and Lakehouse shortcuts. Re-deploy model if mismatched.