Using Lookup Transformation and Cache Transformation in SSIS for Dynamics 365 (using Kingswaysoft)

Recently while working in data migration project, we had a requirement to insert a record in CRM from SQL Database and assign it to the team insert.

For e.g.

We had a Transaction Record that had a Brand lookup in it i.e. n – 1 relationship.

And the Brand record had a lookup of Team in it again n – 1. So basically, while inserting the transaction record we wanted to assign the record to the team of the corresponding brand in it.

So, for this, we had to set the owner id and owner id type field while inserting the record.

And for owner id i.e. team GUID we had to do a lookup on the Brand entity.

To achieve so, we did the following step

Added 2 Data flow task in the Control Flow, one for Caching the Brand entity’s detail and other for using the fetching data from SQL DB, Lookup Transformation task and inserting the data into CRM.

For the first data flow task,

We added the Dynamics CRM Source and fetched the Brand Name and Team Lookup’ GUID field.

name field which will be used for mapping and teamid field whose value we need from it.

Then we added a Cache Transform task with following details,

Now for our second data task flow,

First, we added the OLE DB Source to fetch data from the source SQL View, having Brand (string) column in it.

Then we added the Lookup Transformation task with following properties,

Setting Connection to Cache Connection Manager defined earlier.

Now the most important part, the columns properties. Here we defined the mapping between the Brand field of the SQL View and name field of the Brand Entity of CRM and selected the teamid field as the lookup column whose value we would like to fetch as shown below.

Then we added Derived Column task to add one more column for specifying ownerid type field to be used in CRM Destination Component while mapping. We defined the field type as string and hardcoded the value as “team”.

And as the final step mapped the above fields to the corresponding ownerid and owneridtype field in CRM Destination Component for Create operation.

For ownerid, we selected the below option as we were setting the GUID of the team.

On running the package, we can see the transaction records getting created and properly assigned to the corresponding team of the brand.

The transaction record with Team set as Owner.

Brand record with Team lookup in it.

Hope it helps..

Operation on clone solution failed error during solution import in Dynamics 365

We’d get this error if we are trying to import a solution whose upgrade solution is already there in the target system.

So, either we need to Clone the Solution to remove the upgraded solution or we need to delete the Upgrade Solution. Deleting the Upgrade solution will only delete the solution it will not delete the components as it will already be there in the main solution whose upgrade has been imported.

Hope it helps..

The import of the solution failed – The specified role cannot be updated error in Dynamics 365

We got this error while trying to import managed solution to our TEST environment.

The detail of the error message clearly tells the reason for the error.

The error was because that we had a similar a role with same name in our TEST environment, and in DEV we had renamed that existing role and had created a new role with similar name.

So, while trying to import the solution, CRM was getting confused as it was able to find the role with same name but different id.

To fix this either rename the Role in DEV and export and import it back or rename the role in TEST to and them import the same solution.

Hope it helps..

The solution installation or removal failed due to the installation or removal of another solution at the same time error in Dynamics 365

While trying to install a managed solution we were getting the below error

As the error message suggests, at the same time we had the solution upgrade (Apply Solution Upgrade) going on in the same environment.

Installing the solution worked after the solution upgrade successfully completed.

At times we might face SQL Timeout issue while trying to upgrade solution if it contains large number of components in it.

Hope it helps..

Delete solution components from Managed Solution without “Clone Solution” in Dynamics 365

Recently while moving a managed solution from Development to Test, UAT and Production Environment, we realized the if we increase the version number of the solution manually during export and try importing it, we get the option of Stage for UpgradeApplying Solution Upgrade.

This is basically the same option we get when we clone the solution and use it for deleting the component or working with patch solution.

So basically wanted to check if we can remove components from solution by simply increasing the version number, instead of cloning the solution.

Created a solution in Dev, added a custom entity with a field named test field.

Exported it as managed and imported in the Test (version

Then removed the field from dev.

And increased the version number to before exporting it as managed.

While importing selected Stage for Upgrade and Overwrite Customizations. Maintain customizations should also work.

After successful import, selected Apply Solution Upgrade.

The solution upgrade was successful.

And it removed the field.

So basically, we do not need to clone a solution explicitly in our Dev, we can increase the version number while exporting and select Stage for Upgrade + Apply Solution Upgrade to remove\delete the components.

Hope it helps..

SecLib::AccessCheckEx failed ObjectTypeCode: 2500 AccessRights: WriteAccess error on User Entity UI Settings in Dynamics 365

Recently one of users started getting the below error when he tried to open a record from grid.

Details: –

We checked, and the user was having the Write Access to User Entity UI Settings entity (2500) through the Team’s security role that he was member of but wasn’t having the rights through the security role assigned to him.

The first arrow shows the missing Write access through a security role assigned to the user and remaining are Write access through the Teams he is part of.

To fix the issue we had to give Write access to the user on the security role directly assigned to him. Basically, user needs to have this right explicitly in his role, as it is User specific entity.

The helpful posts

Hope it helps..