Jan Nilsson System owner Dynamics 365

From the latest update for Dynamics 365 F&O to version 10.0.45 we had a failure for three tables whos integration from F&O broke directly after we deployed the F&O upgrade to production. No alerts or errors was given when this occorred. According to Microsoft support this is an issue that will be recurring for every application version updates as well as proactive quality updates for F&O. The solution for this was to delete the affected tables and reconstruct them from F&O again. When this was executed these three tables got back to synchronization again. The severe issue with this was, besides being time consuming, that this lead us to have a downtime for affected PowerBI reports for a minimum of 8 hours due to the amount of data needing to be re:synced from F&O to PowerBI.

A conclusion of this is that we, for avoiding reports down time, need to set resources for always testing the integration between two Microsoft systems when there is an application version update as well as the proactive quality update for F&O.

This needs Microsoft attention to solve this since the impact on the business is critically high

<> We need alerts or available logs for monitor the affected hundreds of tables possibly affected

<> There should be a simpler way for getting the synchronization back without current downtime