Changes

Jump to navigation Jump to search
1,458 bytes added ,  10:10, 26 April 2022
no edit summary
Line 8: Line 8:  
* A guidance for when to do initial sync and not to can be found in MS Docs, [https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/initial-sync-guidance#guidance-matrix Guidance Matrix]
 
* A guidance for when to do initial sync and not to can be found in MS Docs, [https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/initial-sync-guidance#guidance-matrix Guidance Matrix]
 
* There is an article describing the linking process, written by Faisal Fareed: [https://daxture.blogspot.com/2020/11/steps-to-follow-when-refresh-dual-write.html Steps to follow when refresh dual-write integrated environments (FO and CE)]. That is a good go-to article each time you need to re-link environments.   
 
* There is an article describing the linking process, written by Faisal Fareed: [https://daxture.blogspot.com/2020/11/steps-to-follow-when-refresh-dual-write.html Steps to follow when refresh dual-write integrated environments (FO and CE)]. That is a good go-to article each time you need to re-link environments.   
 +
 +
== Re-link Dataverse-FnO ==
 +
The list below is available here all thanks to Faisal Fareed and his article which was the inspiration to the list. Source environments below means the environments which we want to copy from (e.g. Prod). Target enrironments means the environments we want to copy to (e.g. UAT/Test).
 +
 +
1. Go to FnO (target environment) Data Management -> Dual Write and stop all jobs.
 +
2. Copy from FnO source environment to FnO target environment and Dataverse source environment to Dataverse target environment. (Note, we assume that the source environments are linked). 
 +
3. Go to FnO (target environment) Data management > Dual write and Unlink environments.
 +
4. Delete data from the following tables in FnO if data exists
 +
DualWriteProjectConfiguration - e.g. use URL <Environemnt URL>/?mi=SysTableBrowser&prt=initial&limitednav=true&TableName=DualWriteProjectConfiguration&cmp=<CompanyId>
 +
DualWriteProjectFieldConfiguration- e.g. use URL <Environemnt URL>/?mi=SysTableBrowser&prt=initial&limitednav=true&TableName=DualWriteProjectFieldConfiguration&cmp=<CompanyId>
 +
5. Delete data from DualWriteRunTimeConfiguration Table in Dataverse, e.g. using Advanced Find.
 +
6. Link the target environments
 +
7. Apply Microsoft Dual-Write solutions and custom solution if any
 +
8. Start jobs. No init sync needed if copied from both Dataverse and FnO environments which were linked. If copied only from one the two Dataverse or FnO, then also do an init sync.
    
== Reading list ==  
 
== Reading list ==  
   
Here follows some links which might be worth taking a look at when learning how to set-up dual-write.
 
Here follows some links which might be worth taking a look at when learning how to set-up dual-write.
  

Navigation menu