Nishant Rana's Weblog

Optimum Batch Size while using SSIS Integration toolkit for Microsoft Dynamics 365

Hi,

https://nishantrana.me/2018/12/19/optimum-batch-size-and-thread-while-deleting-records-using-ssis-integration-toolkit-for-microsoft-dynamics-365/

Recently while working in a data integration task, we were evaluating the performance of using KingswaySoft’s Dynamics 365 Toolkit from within Visual Studio by trying out different possible combinations of batch size and threads.

The environment was CRM Online and had concurrent ExecuteMultiple max limit set to 20.

By default, it is set as 2 for online, but we can raise support ticket with Microsoft to get this limit increased. However, we need be very careful while using them as large number of ExecuteMultiple running in parallel might degrade the performance.

https://msdn.microsoft.com/en-us/library/microsoft.xrm.sdk.deployment.throttlesettings.executemultipleperorgmaxconnectionsperserver.aspx

Below are the 2 settings that we played around in the CRM Destination Component

These are the results we got with different batch size and thread.

Message Used– Upsert.
Total Number of Records – 20000.

It clearly shows that having batch size as 100 gives the best result.

And this is what is recommended by KingswaySoft as well.

https://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-dynamics-365/faq

Hope it helps..

Fixed – CRM service call returned an error: The server is busy and the request was not completed. Try again later while inserting records using CRM Destination Component of KingswaySoft’s SSIS Integration Toolkit for Dynamics 365

While running one of our package we got the below error in few of the records

“CRM service call returned an error: CRM service call returned an error: The server is busy and the request was not completed. Try again later. (Error Code: -2147180543, Detail Message: The server is busy and the request was not completed. Try again later.)”

“CRM service call returned an error: CRM service call returned an error: The request channel timed out while waiting for a reply after 00:01:59.7991956. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. (Error Type / Reason: Timeout)”

One way to get around this error is to increase the Timeout (secs) in the Service Timeout Setting of CRM Connection Manager.

We updated it to 600 seconds and the number of records that failed got drastically reduced.

Also make sure that following option is checked

Hope it helps..

Lookup not getting set while using CRM Destination Component of KingswaySoft’s SSIS Integration Toolkit for Dynamics 365

Recently while inserting a custom entity (Transaction) records using the CRM Destination Component we realized that Contact’s lookup was not being set.

We were using Alternate Key to set the lookup as shown below

To get it working we had to uncheck the Remove Unresolvable References option from the Optional Settings of CRM Destination Component. It seemed that it ignored it, even though values were there for the GCR (alternate key field) in the input source.

https://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-dynamics-365/help-manual/crm/destination

I think it might not be working as expected in case if lookup is done using Alternate Key.

BTW, I would strongly recommend using KingswaySoft’s SSIS Integration Toolkit for any or all data integration tasks. It is definitely the best tool out there.

Give it a try à

https://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-dynamics-365/download

Hope it helps..

Dynamics 365 CE (CRM) Data Anonymization: Anonymize sandbox data (copied from production) to meet data security standards like GDPR

Prashant Kumar Maurya

We all have faced situation in when we need to replicated Dynamics 365 production environment to a lower/sandbox environment for distinct reasons like

To reproduce and debug productions issue in a lower environment.
To create a preprod environment replica of production environment.
To create a development environment from production environment. etc.

And to protect confidential customer data we do masking of confidential information before we share this environment to dev/test/support/another team. This masking activity is very tedious and time-consuming, one can do it manually or can right some code logic to do so.

Thanks to KingswaySoft, they have created an excellent SSIS component “Data Anonymizer” that can make things simple.

How to use Data Anonymizer Step by Step: I assume that the person reading this blog has basic knowledge of SSIS, as it is very focused on Data Anonymizer component.

Before you start you also need another component

View original post 162 more words

Fixed – View Designer not showing SSIS Package in Design mode in Visual Studio

Time to time we’d see our Package not opening in Designer mode in Visual Studio.

To fix this,

Add the package again in the solution or restart the Visual Studio.

Hope it helps..

Security Nuances with Manager Based Hierarchy in Dynamics 365

Interesting read on Manager Based Hierarchy ..

Debajit's Dynamic CRM Blog

Manager Hierarchy was introduced way back with 2015 Online Update 1. And you might be wondering why this blog after years this feature has been introduced?

Well I can assure you, you won’t be disappointed after reading this blog. In this blog I will explain in detail the manager security nuances from my personal experience with project implementations and training. I am not going to explain how Manager security works. I am just going to explain the security nuances and how it works in multiple scenarios.

To explain my point, I have the below data set-up in my environment.

To put in simple terms, any of the records which does not meet the above four conditions is not affected by Manager Hierarchy. So the records which the reportee gains access due to his security prvileges (Business Unit/ Parent child/ organization) are not affected by this. Confused? Don’t worry. We will…

View original post 365 more words