Process Optimizations is a new feature added in the CDS / CRM Destination Component of KingswaySoft’s SSIS Integration Toolkit as part of November 2020 Release. Check other posts on SSIS and Dynamics 365 https://nishantrana.me/2020/10/16/ssis-kingswaysoft-and-dynamics-365/ These options if enabled, will turn off or disable plugin, workflow, entity auditing during pre-execution temporarily, during the writing process, and […]Process Optimization – Dynamics 365 CE / CRM / CDS SSIS Integration toolkit – KingswaySoft
In my previous blog I explained the issues that I faced while POA entity migration. Here I will explain the whole process that I followed to migrate the personal views with sharing information. I used kingsway soft adapter for my migration process.
We have 2 steps to migrate the data
- Source CRM –> Intermediate database.
- I enabled “Data Export Services” on the source instance to push the data into intermediate database.
- Since “userquery” entity is not available in “Data Export Services”, I Designed a simple SSIS Package with source (Dynamics CRM) and destination (OLE DB) components.
- We have to impersonate the owner of the personal view in the Dynamics CRM Source component to read this information.
- So we have to run this package multiple times based on the user count.
- Intermediate database –> Target CRM
- Designed 2 more SSIS Packages to push “userquery” and “principalobjectaccess” (share) information to Target CRM instance.
- userquery package is pretty straightforward with source (OLE DB) and destination (Dynamics CRM) components. So I am not explaining much about this package.
- But we faced some issues which I explained in the previous blog while migrating “principalobjectaccess” data. I followed the below process to migrate this data.
- Created a SQL View in intermediate database on “principaobjectaccess” table by joining the “userquery” table to get the owner of the personal view.
- I used this view in “OLE DB” source component to read the data.
- This owner field should be mapped to “impersonateas” field in the destination component, so that internally the share request will be executed under owner context.
- Batch size should be 1 in the Dynamics CRM Destination component, otherwise it will not process all the records.
This process is same to migrate personal charts (userqueryvisualization) and dashboards (userform) also. Hope this information is helpful.
In our project we got a requirement to migrate shares of personal views. We all know that share information will be stored in “principalobjectaccess” table. I faced couple of issues while migrating this data and I want to share this information here.
Issue 1: You can’t share a personal view owned by other user. To solve this issue, Kingsway soft provided a field called “impersonateas” which should be mapped to owner of the personal view (you can get this information by join the userquery table with POA table). So that the share request will be executed under owner context.
Issue 2: After Issue 1 is fixed we faced another weird issue that the package is only processing only 1 share in target instance irrespective of no.of records from the source. After a bit of research, we identified this is because of the “Batch Size”, after changing the batch size to 1 with out any threads it processed all the records from the source. I hope it is because of the impersonation we are using in the package.
I hope this information helps some one who wants migrate sharing information of persona views/charts/dashboards.
Recently when I am running a background process I got the below error on one of the customer’s instance.
The async operation was skipped because the org is in ‘Disable Background Processing’ mode
After a bit of research I understand, we can disable the background process execution from admin control. Follow the below steps to enable / disable background processing.
- Navigate to https://admin.powerplatform.microsoft.com
- Select the Instance that you want to make this change.
- Click on “Edit” to open the settings screen where you could make this change.
- Change the “Background operations” setting as per your requirement.
I found a very good article to use forms as a Dialog. Hope it helps everyone….
Column Comparison is one of the best features that has been recently added to the product.
Column comparison allows us to compare values of 2 different columns in our query be it Fetch XML, Web API, or through SDK API.
Sharing some of the basic examples that we tried using our favorite FetchXML Builder
- If we run the following query “Find all contact which has the first name equal to the last name”
The result –
- Find all contact where the first name is not equal to last name
The result –
The operators supported are –
- Only 2 columns can be compared.
Only compatible attribute types can be compared.
E.g. “Find all contact where the first name is equal to address 1 city”
It works as both are string attributes.
- If we try comparing text field with options set, we…
View original post 111 more words
This blog is to help fellow consultants to start their journey on PowerApps. We all know how easy it is to put together a screen on Canvas Apps but as and when we need a specific action on it or from it; we fall short of formulas/functions. That’s because we never required these formulas in Model Driven Apps.
But as Business/Functional Consultant, you want to deliver value to your client, make their life easier, Don’t you?
I am sure you do, so here I am providing you with 20 essential functions you must know as a functional consultant. This can be a starting point for you; well, Microsoft is trying hard for Business Users and Functional Consultants to get in the rink of Power Platform. Their learning path is specially designed for Business Users and Functional Consultants, check it out here Learn PowerApps.
All formulas below are…
View original post 504 more words
In the previous post, we covered conditional access based on the device platform, here we’d look into how we can use the network location to block the access.
We can either use IP ranges or Countries / Regions for defining the location.
Login into the Azure Portal
Navigate to Azure Active Directory – Security – Named locations to define the location.
Here we are adding a new countries location record.
For the new location, we have selected India and UAE.
Next click on Conditional Access to define a new policy.
For Users and groups, we have selected a user named testuser1.
For Cloud Apps or actions, we have selected Common Data Service.
For Conditions, we have specified Locations condition with the Restricted Locations record that we had created earlier.
For Access Controls, we have selected Block access.
Enable and create the policy.
View original post 57 more words
Today while exploring the CRM, I found “status reason transitions” option of status reason field. This option is introduced many years back but I haven’t noticed. Status reason transitions are an optional additional level of filtering to define what the status reason value can be changed to for each status reason. That means it will restrict the users to select the status reason which is not valid based on current status reason. Follow the below steps to configure this in your environment.
- Open the Default solution.
- Navigate to the entity (Case for example).
- Go to Fields and open “statuscode” field.
- Click on the “Edit status reason transition” button on the top.
- A window will open to configure the status reason transition . The Current Status Reasons are available on the left and for each of the Current Status Reason you can specify the available New Status Reasons.
- Select “Enable Status Reason Transitions” check box and add the new status reasons based on your business need.
- Save and publish the changes.
In the above example, one of the business scenario is, I will not allow the users to select “Problem Solved” status reason from “On Hold”. User has to change it to “In Progress” in order to move to any other status reason.
Like this you can configure all your scenarios based on your business needs. This can be configured on both System and Custom entities.
In one of my previous post, I explained about the navigation property naming issue when working with Lookup fields using the WebAPI endpoint in “CDS/CRM Connection Manager”. Recently, I got a mail from Kingsway Soft support team with a Hotfix to resolve this issue. I installed this Hotfix in my machine and ran a simple package successfully to update custom lookup (account) on Contact entity.
This Hotfix is part of the most recent official release (188.8.131.524). You can download this from the below link.
So, I would recommend everyone to use WebAPI endpoint instead of SOAP in “CDS/CRM Connection Manager” due to the fact that SOAP endpoint is deprecated and no longer supported by Microsoft.
You can find all enhancements of the recent official release (184.108.40.2064) in the below link