Forum Discussion
Report return error in visual after promotion in deployment pipeline, that is not seen in 1st stage
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.
Community SupportHi Scalkins1743 , hope you are doing well. Just wanted to know if your issue has been resolved through your support ticket with Microsoft? If so, we would greatly appreciate it if you could share the insights here, as they may benefit others with similar issues.
If you have any other queries, please feel free to raise a new post in the community. We are always happy to help. Thank you.
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.