Skip to main content

Posts

Showing posts with the label PowerPlatform

MS D365 FinOps: How to create new LCS project and deploy Tier 1 (DEV) VM - Even you are not a MS customer or partner :) - Part I

Scenario: You are willing to work on Microsoft Dynamics 365 Finance Operations  product and want to get your hand dirty with some development. You are hearing so much about this product but never got a chance to work on this MS ERP.  Andre wrote a detailed post on how you can setup a trial environment for MS D365 Finance Operations Solution: With this post I will explain a step-by-step guide on how; to create your own LCS project to deploy a new Tier 1 VM to log on to Azure Portal to access Power Platform environments to create your own power app and use other features to deploy solutions in Power Platform to integrate with Finance Operations NOTE: You would need Azure Subscription to deploy VM First create new domain to perform all above steps - its easy just follow following steps 1. Open this site Office 365 E3  in cognitive mode or as guest and go with Free Trial option 2. Fill in details - you can use your personal email or sign up for a new email account and use t...

Dual-write learning series - Dual-write initial sync is the data integrator

One of the features of the dual-write is initial sync where you copy data from the source app (Finance Operation OR DataVerse) to the target app  (Finance Operation OR DataVerse) depending on the selection in Master for initial sync option.  This initial sync is the Data Integrator service running behind the scene and copies your data over. You configure the application id for data integrator and add it both apps ( Finance Operation OR DataVerse ), I have documented it my previous post  The Dual Write implementation - Part 2 - understand and action pre-requisites Master for initial sync can be either Common Data Service (Dataverse) or Finance and Operations apps. For example, If I choose Finance and Operations app in below example where I am syncing Functional Locations then all records will be copied from Finance and operations to Dataverse. Initial Sync is a full push means if an individual row fails to sync, you cannot resync only failed ones.  If the initia...

How to run dual-write table map when underline entity table is setup under cross-company data sharing policy

Scenario:   Project groups are shared across all legal entities in  D365 finance & operations app so have setup under one of the cross-company data sharing policies. You are also required to setup dual-write table map for project groups to sync from FO to CDS. However, you get following error message when you try to Run the table map "Copying pre-existing data completed with errors. For additional details, go to initial sync details tab." Follow these steps to overcome this issue as a workaround.  Steps to follow: Disable cross-company data sharing policy where ProjGroup table has been used Choose Yes at next pop up window Go to Data management > Dual write > select Project Groups table map and Run Enable cross-company data sharing policy for project groups Choose No at the next pop up window unless you want to copy data across all companies

Steps to follow when refresh dual-write integrated environments (FO and CE)

Scenario:   The D365 finance & operations app is linked to Common Data Services through dual-write in development or sandbox environments. You are required to refresh databases in D365 FO and CDS both from another production environment (dual-write integrated (linked) environments in the scenario) Steps to follow: Before initial refresh, log on to target environment Go to Data management > Dual write and stop all jobs Refresh FO and CDS environments from the same integrated source environments Go to Data management > Dual write and Unlink environments Clean data from following tables in D365FO if data exists DualWriteProjectConfiguration - A sample URL would be like this to access tables from D365FO environment <Environemnt URL>/?mi=SysTableBrowser&prt=initial&limitednav=true&TableName=DualWriteProjectConfiguration&cmp=<CompanyId> DualWriteProjectFieldConfiguration- A sample URL would be like this to access tables from D365FO environment <En...

Dual-write connection set error: An item with the same key has already been added

If you happen to see this error message then you have duplicate records in cdm_company entity in CDS environment. Check for cdm_companycode field this is normally not allowed but have a look and delete the ones with duplicates.