Over a month ago, during the MEC process in our company, a Data Mart Reset was performed by another team. The reset took approximately three days. However, once it was completed, we discovered that the financial reports were showing incorrect balances.
We raised a support ticket with Microsoft, and their recommendation was to perform another Data Mart Reset. This process also took several days due to the large volume of data — we have over 500 million transactions in the system. At that point, no one raised concerns about whether such a reset was appropriate for a dataset of this size.
Shortly before the most recent MEC, we were notified that the reports were still not showing correct data. We decided to run another Data Mart Reset, starting on Friday afternoon two weeks ago, hoping it would complete over the weekend.
Unfortunately, the process is still running as of today. Meanwhile, a colleague of mine raised an unrelated ticket with Microsoft because she did not have access to Report Designer. The Microsoft support agent assisting her noticed that report generation was blocked and unblocked it — but this action did not resolve the underlying issue with the incorrect balances.
We are now going back and forth with Microsoft Support. They claim the integration has completed on their end and that reports can be generated, which, in their view, means the issue is resolved. However, on our end, integration is clearly still ongoing, and although reports can be generated, the data is still incorrect.
We have provided Microsoft with multiple screenshots, including the one below, but during a recent support call, they seemed unfamiliar with the issue. In fact, they even asked us how we navigated to the screen in Report Designer to view the integration status.
My question is:
Has anyone experienced a similar issue, and if so, do you have any advice on how it was resolved?
Alternatively, does anyone know of a specific Microsoft contact or team that could assist with issues related to large-scale Data Mart integration?
We have developers on our side who are actively involved, but it appears that resolving this issue will require Microsoft's internal tools or intervention.
Thank you in advance for any help or suggestions.
