Tricks

Quick overview of Dataverse Field Level Security:

Introduction

Field level security in Dynamics 365 allows administrators to control access to specific fields within an entity. This means that certain users or teams can be restricted from viewing or editing certain fields, even if they have access to the overall entity.

It is also possible to use Field Level Security Profiles to group fields together, this way you can assign a security profile to multiple users or teams at once.

Are you working with CRM on-premises and developing a standalone web resources without CRM form ? You can face with this trouble and this article is for you.

Are you migrating CRM on-premises to version 9.1? Are you facing the issue and looking for a workaround? This article is for you.

Microsoft.PowerPlatform.Dataverse.Client : IFD + ADFS Mode not supported !

Valid only at the time of writing this article on 20.11.2022

When creating a ci/cd pipeline for your project, at some point you have to define a connection to your environment. In case of Dataverse, the connection string will contain clientid and client secret values. It's always a good idea to store secret values in a secure place, instead of putting them in clear text into your pipeline definition file (yaml) and potentially pushing them into your code repository.

Azure DevOps provides you a number of possible solutions to address just that: