I found the below article very useful to understand the api request limits.
Search this view capability which was added in the product with 2020 Release Wave 1, searches on the fields specified in quick find view, but takes into consideration the selected view definition, when performing the search.
This is enabled by default.
Here Search this view will perform the search within the selected view i.e. All Contacts in this case.
The results show 3 records found within the All Contacts view, for the search term “alex”
The same search term returns blank in the case of Inactive contacts is selected.
The same applies to the sub-grids
To turn off this, select Yes for Use quick find view of an entity for searching on grid and sub-grids from General tab of System Settings
After applying the above change, we can see the text renamed to Quick Find within the Search Box.
Searching now, irrespective of the view selected, will perform the…
View original post 28 more words
Was going through the Model-Driven Apps documentation and found the below article
It talks about a Check access button on the command bar of a record which will list down all the rights/access/privileges on that particular record.
And also how the user has got those accesses, through security roles directly assigned or through the team the user belongs.
We can also check the access of the other users as well through user lookup.
More on Access in Dynamics 365
Hope it helps..
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
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
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.
At times we need to generate sample data for our entities in Dynamics 365 for various reasons, performance testing is one of them.
Data Spawner component which is part of KingswaySoft’s
SSIS Productivity Pack provides us the most efficient way of doing so.
Download the component here –
Let us generate the sample data for Contact Entity.
Add the Data Spawner component to the Data Flow along with the CDS Destination component in the integration service project.
Double click the Data Spawner to open the editor.
Click on Add + button to specify the columns, here we have specified four different columns.
We have kept the name for each of the columns, same as the schema name so that it is easy to map them in CDS Destination.
For the First Name column, we have specified Data Type as nvarchar and Spawn Type as the First Name, which will…
View original post 180 more words