Posts in this category.
For a long time, Developers for Dataverse don't have an official way to use third-party libraries when creating plugin(s). If we want to reuse existing code, the only official way to do it is to use the Shared Project which is limited to the code that we own + the IntelliSense in...
When you are using DataverseServiceClient, we can see the constructor where we can pass an instance of ILogger. The purpose of this, of course, is to get more information regarding what is happening in our system (you also can monitor the performance). Depending on the scenario...
When I scanned Microsoft.Xrm.SDK namespace from Visual Studio, I found an exciting extension in the ContextExtensions class. In there, we can discover InputParameterOrDefault<T> that accepts a string parameter. Without further ado, let's go to my testing about it! Demo 😁 I...
Celebrating the GA of DataverseServiceClient, let's talk about how to implement concurrency (if there are two users updating the same data at the same time, the system must ensure only the first update success and make fail the other) using an out-of-the-box feature. From...
Recently, my friend (Low Ming Hua) told me about an interesting scenario related to the Field Security Profile. He needs to enable lots of attributes and set the Field Permission to specific teams (he also shared with me his code and I modified it!). For those who don't know, we...
When I read this documentation about Service protection API limits, I was curious about the easiest way to get the error to validate the code in the documentation and enhance it. I read the documentation and found out about Dataverse search, which has a stricter policy (one...
The getUserPrivilege is a function that will return canRead, canCreate, and canUpdate. This function correlated with the Field Level Security feature making it suitable to check if users have enough privilege to run our custom function on Javascript. For example, we have below...
When we have already set up a Virtual Table/Entity in the Dataverse, sometimes there is a scenario when a data is being updated in the source system, it also needs to trigger the Dataverse Event (that contains our custom business logic). Today, we will learn how to enable Virtual...
Do you know that we have the Virtual Connectors in Dataverse (Preview) solution in the AppSource that can let us configure and create Virtual Entity easily? We can do the CRUD (Create-Read-Update-Delete) operation directly (I tried the SQL Server connection) and it works...
Do you notice when we create a Lead and qualify it in Dynamics CRM, the out-of-the-box feature will convert the Lead to Contact (all the data that was input in Lead, automatically populated in the Contact)? And sometimes, we are also being requested to make the same feature...