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.
Memorable MemberScalkins1743It really sounds like you are extremely deep into the weeds here. I would suggest looking at the Known Issues with Power BI and Fabric and see if anything fits. You can also open a support ticket there if necessary.
Couple questions though. One, do any parameters change at all between Test and QA for either pipeline? Currently, it sounds like everything is exactly the same between Test and QA other than the workspace. Two, what happens in Prod?
gerald there are no defined parameters for these semantic models. We have not promoted the semantic model to PROD, due to this issue in QA. As this is a new solution, and the content has not been released to end users with a previous version, I can promote this to PROD and see if the behavior is consistent there as well and reply with an update.
I've opened a support ticket, and will check out the known issues. Thank you for both suggestions!
- GeraldGEmerick
Shahid12523 My pleasure! Would be interested to know if you get the same behavior in PROD. Hope you get it resolved!!
v-hashadapuCommunity Support
Hi 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.