Easy Dynamics 365 Document Updates with Azure Information Manufacturing unit

Within the realm of knowledge migration and integration, Azure Information Manufacturing unit (ADF) serves as a sturdy device for transferring and reworking knowledge throughout varied programs. A typical state of affairs entails updating present information in Dynamics 365 (D365) utilizing the inner GUID (Globally Distinctive Identifier) with out counting on extra migration references. This text will information you thru the method of updating a D365 Account document with new phone and deal with info utilizing ADF.

Understanding the Inside GUID in Dynamics 365

Every entity inside Dynamics 365, corresponding to an Account, Contact, or Alternative, has a novel identifier often called the GUID. For instance, the Account entity makes use of the sector `accountid` as its GUID. This identifier is essential for exactly focusing on information throughout updates.

Let’s assume we’ve got an present Account in D365 with the next distinctive identifier.

A1B2C3D4-5678-90EF-GH12-IJ345KLMNOP6

We have to replace this Account with the next new particulars.

1. MainPhone: +123456789
2. Address1Street1: Suite 789
3. Address1Street2: 123 Elm Avenue
4. Address1City: Springfield
5. Address1Postalcode: SP1 2AB

Updating the Account Document
 

1. Arrange Supply Information in Azure SQL Database

Begin by guaranteeing that the up to date info is saved in an Azure SQL Database. This desk ought to embrace the D365 Account’s GUID and the brand new values you plan to use. For instance, the desk would possibly comprise the fields `MainPhone`, `Address1Street1`, `Address1Street2`, `Address1City`, `Address1Postalcode`, and the `accountid`.

2. Create Datasets in Azure Information Manufacturing unit

1. Supply Dataset: This dataset factors to the Azure SQL Database containing the up to date Account info. Make sure that the schema is imported to facilitate straightforward mapping later.
2. Sink Dataset: This dataset connects to the D365 Account entity. It’ll function the goal for the replace operation.
   

3. Configure the Copy Exercise

1. Add a Copy Exercise to your ADF pipeline.
2. Set the Supply to the Azure SQL Desk containing the Account knowledge.
3. Set the Sink to the D365 Account dataset.
4. Within the Mapping part, map the fields out of your SQL desk to the corresponding fields within the D365 Account entity.
   

4. Configure Upsert Operation

1. Within the sink configuration, set the “Write Conduct” to Upsert.
2. You possibly can depart the “Alternate Key Identify” as None since you’ll be utilizing the `accountid` GUID for the replace.
   

5. Execute the Pipeline

Operating this pipeline will replace the desired Account document in Dynamics 365 with the brand new phone and deal with info from the Azure SQL Database.

6. Confirm the Replace

After executing the pipeline, you should utilize D365’s Superior Discover to verify that the Account document has been up to date with the brand new values as anticipated.

Conclusion

Updating Dynamics 365 information utilizing Azure Information Manufacturing unit with the inner GUID is a streamlined method that eliminates the necessity for alternate keys or extra migration references. By following the steps outlined above, you possibly can effectively replace your D365 information with precision, guaranteeing knowledge consistency and accuracy throughout your programs.

Thanks for Studying!! DO Like And Upvote!!