Category: CRM

Informatica Cloud has recently released new connector for integration with Dynamics 365 named Dynamics 365 for Sales Connector, which uses Web API of Dynamics 365.

Below is how we specify the details of the connection –

Because of lack of documentation for the new connector, while trying to insert a record inside CRM and trying to setup a lookup field we struggled a lot.

Eventually, we realized the format that is required for setting the lookup field.

EntitySetName:(GUID)

i.e.

sab_fash_categories(72e0b837-e060-4a5c-b831-0e8266dd9a56)

Here sab_fash_categories is the EntitySetName of the custom entity sab_fash_item and it is being used as a lookup in another entity.

For the older version of the connector that used OrganizationService, the documentation is available which specifies the following format for the lookups

{SchemaName:GUID} i.e. the way we specify while setting EntityReference field

https://kb.informatica.com/proddocs/Product%20Documentation/6/IC_Spring2017_MicrosoftDynamicsCRMConnectorGuide_en.pdf

Hope it helps..

Recently while working with a Solution Patch we came to realize one of its limitation (or feature) which we weren’t aware of.

If we are trying to update a component through the patch, and that particular component has been customized in the target environment ( through default solution in case of managed), the update won’t work on that component.

Let us take a simple example to understand this.

Below we have created a solution with one workflow in it named Test Process.

Now let us export the solution as managed and import it in Test.

Now back in our DEV let us rename the Process and create a patch for it and import it in Test.

https://nishantrana.me/2016/09/22/creating-patches-solution-management-in-crm-2016/

We can see the update in the name after applying\importing the patch.

Now let us go back in our DEV and make some update in the name of the process and import it again in the Test.

We have selected the option of overwriting customizations here.

We can see the update in the TEST after importing the patch.

Now comes the interesting part, in the TEST environment, go to Settings – Customizations and rename the Process. Here we have appended “Updated” in its name.

Now let us import the same Patch Solution back in our TEST with Overwrite selected.

Unexpectedly, we do not see any change, the process is unchanged in the TEST even after importing the patch with Overwrite option. We expected it to be renamed to Test Process Patch Version 1 as it was in the patch solution, instead, it has the suffix Updated to it i.e. the changes that we made directly in the TEST through default solution.

The way we can now update it from DEV is to clone our solution there.

Import it to TEST and apply Solution Upgrade.

Below we can see the new version imported into the TEST and as expected the Process renamed to what it was in DEV.

Hope it helps..