Posted in Dynamics 365, Dynamics CRM, Microsoft Flow

{No code approach} Delete attachments from corresponding SharePoint folder when a record is deleted in CRM using Microsoft Flows

REAL TIME SCENARIO – MICROSOFT FLOW

Debajit's Dynamic CRM Blog

Off late, I have been working with Microsoft flow and boy! I am liking it. It is cool and specially considering the fact that it simplifies whole lot of stuffs that you would normally require to write lot of code, make it even more appealing.

So here I was with a requirement.

There was OOB CRM-SharePoint integration enabled and the client wanted that whenever an entity record is deleted from CRM, the documents in the corresponding SharePoint folder should be deleted as well.

Now the OOB behavior does not support that. Even if you delete the record, the folder corresponding to that is present in the SharePoint path with all the documents.

So what are my options here. Well some custom code that would run when the record is deleted in CRM and that code would be responsible for deleting the documents from the SP Folder. On top of that…

View original post 942 more words

Posted in Dynamics 365, Dynamics CRM

Under the Hood – There’s a Dynamics 365 App for that

Excellent post.. Deep Insights about Dynamics CRM evolution
#Dyn365 #NewFeatures

Dynamics 365 Northern Ireland

Microsoft has surely been looking at Salesforce for the past few years, feeling somewhat envious of their ‘apps’ market. If you take Salesforce at their word, they have over 1.4 million registered developers, so the apps market for Salesforce is clearly not a flash in the plan.

With the recent launch of Dynamics 365, there appears to be a concerted effort at Redmond to build an ecosystem around Dynamics 365, but how has this been implemented and what do application developers need to know?

365 Apps v Solutions

Back in the day when solutions were introduced in Dynamics CRM 2011, you could see the start of an effort by Microsoft to have proper application lifecycle management around Dynamics CRM customisations and configurations.

solutions CRM 2011 Solutions

Unmanaged solutions were a way a developer could keep track of their many bits and pieces within CRM. Managed solutions were way of packaging…

View original post 1,198 more words

Posted in Data Migration, Dynamics 365, Dynamics CRM, SSIS

Data Migration SSIS Tips – 1

Recently we were migrating records from Source system to staging database and then to Dynamics CRM 2016 using SSIS.

Few issues are encountered while we migrating the large number of records.

Script component:

Some time we might require to use the script components because some conversion is not possible/not easy with SQL. In this case, number of columns which you processing will affect performance of the package.

How to improve ?

Avoid using the script component as much as possible

We can utilise the BDD – Balanced Data Distributor. It helps to parallelize the data flow. if you new to this, here is the link for more information (BDD – Balanced Data Distributor)

Try to use synchronised transformation. It’s better compared to Asynchronous. Ideally it’s up to the requirement. for better understanding, here is the link (Synchronous vs Asynchronous

Derived column:

The number of columns in derived columns also affects the performance of the package.

Then how to ?

Try not to use the derived columns as much as possible

If there is a need, we have to use. then use multiple “Derived columns” component for manipulation. Instead of doing all the manipulation in single “Derived column”. Significantly it will improve the performance

Data Conversion:

This component in SSIS which will help to convert the data type of column to another compatible data type. It’s just drag and  drop and easy to use. when you really care about the performance, then here we go. It does maintains the old column as well as converted column too.

Then how to ?

Try to do the conversion at source itself. It’s best as package don’t need to maintain the duplicate of it.

If the conversion is not possible at source, do the manipulation at staging.

Always, i prefer to have the manipulation in Stored Procedure. It really faster and it will not impact the performance as much as others.

Do share your knowledge on these..

Keep Sharing …

Posted in Data Migration, SSIS

Unable to create the type with the name ‘CRM’ (Microsoft.SqlServer.ManagedDTS)

Case

Some cases, we will be developing the SSIS package with third party component (custom dll’s) to connect or integrate with certain applications. In that case, while deploying the packages to different server, we need to install third party component (custom dll’s) as well. Rarely we will be getting error in deploy the package.

Continue reading “Unable to create the type with the name ‘CRM’ (Microsoft.SqlServer.ManagedDTS)”