Not only does the form component control allows you to edit records directly from another record's main form, it might also be a good replacement for field level security.
In model-driven applications, forms often contain many fields spread across multiple tabs and sections, which can make it difficult and time-consuming to find key information. Navigating between these tabs slows productivity and increases the risk of missing important information. Finding key insights quickly can be a challenge.
Having clean data in Dataverse can be tricky. One of the challenges is detecting and managing duplicate records.
With out-of-the-box tools you can implement duplicate detection rules or create alternate keys.
If you are a developer, you can implement a custom validation in a plugin.
In this article we will focus on out-of-the-box features (duplicate detection rules and alternate keys) and compare them.
Dataverse Managed Environments Deep Dive:
Managed environments is a set of features that allows administrators to manage Power Platform at scale with more control, less effort, and more visibility.
List of features available with Managed Environments for now (18/09/24) :
Dataverse Elastic Tables Deep Dive Tutorial
Said to be the "Super Heros" of the information world, that they're super fast and can store lots of information and that they're a game changer for storing massive loads of data.
I went to undercover what's behind the scenes of this Elastic Tables feature and check if the rumours are fake or not!
When a user is deleted from the Microsoft 365 admin center, the user isn't removed from Dataverse environments in which it is active. Instead, the user's status is set to Disabled in the Power Platform. And you do have the possibility to delete it.
As a consequence many disabled users can pile up in the Power Platform.
With the feature 'Delete Disabled Users' Microsoft has introduced the possibility to permanently delete disabled users from the Power Platform.
Dynamics 365 : Dataverse Preferred solution
By default, unless already in the context of an unmanaged solution, all changes performed in your Power Apps environment (creating a table or column, updating a form, ...) are stored in the solution named Common Data Services Default Solution.
With the preferred solution you can specify a solution to which all your changes, that are made outside of the context of the unmanaged solution, should be automatically added.
Power Apps : Smart Email Address Validation
Traditionally, the existing Email column type has only basic email validation: a valid email address consists of an email prefix (left part of @ symbol) and an email domain (right part of @ symbol). So it is a very basic validation.
With smart Email address validation, the Email column comes with better validation that includes reasons for the column being invalid.
Smart Email address validation detects the following issues:
The Alternate keys provide an efficient and accurate way of integrating data with external systems. It’s essential in cases when an external system doesn’t store the Globally Unique Identifier (GUID) IDs that uniquely identify rows in Microsoft Dataverse.
Some of the benefits of the alternate keys feature include:
