Carina M. Claesson

This is part five in a series of posts, you can find the first one here. In the dual-write projects I have been involved in, I have had the possibility to exchange ideas with people both within the projects but outside of the projects as well. Community when at its best, people sharing and are willing to exchanged ideas even though not at the same company. In this post, I’ll highlight the Yammer group dedicated to dual-write and let you in on other good-to-know info and sources of information and inspiration.

This is part four in a series of posts, you can find the first one here. In the dual-write projects I have been involved in, either the customer has been live on the F&O side or it has been a new implementation. Even though new implementation, the F&O side has been further ahead than Dataverse and the introduction of the dual-write synchronization.

Both cases have caused the following difficulties: UAT constantly being updated from production and dual-write settings and sync all messed up. In this post I will share what needs to be done when a db refresh is done on the F&O side and you are running dual-write with a linked Dataverse environment.

This is part three in a series of posts, you can find the first one here. In part two we looked at linking environments together. When you have linked F&O to a Dataverse environment with the purpose to start utilizing dual-write, it’s time to think about your specific integration scenario and what templates to start from. Most likely you will need to make modifications to mappings and create your own table maps.

This is part two in a series of posts, you can find the first one here. You might have heard of One Dynamics One Platform. Until we are there, we live with F&O in LCS and in order to utilize the Power Platform integration and e.g. dual-write, we need to handle the linking parts ourselves. In this post I will share my findings related to linking environments into pairs, F&O and Dataverse.