Validate Email address on Email field in Model-Driven Apps | [Preview]

As part of various implementations, often you’ll need to ensure that the field validation is in place.

Note: Please note that this feature is still in Preview at the time of writing this post.

Enable Data Validation in Power Platform Admin Center

Here’s how you can enable Data Validation for Email fields in Power Platform Admin Center

  1. Once you have the correct rights in Power Platform Admin Center (https://admin.powerplatform.microsoft.com/environments), select the Environment you want to enable Data Validation for.

  2. Now, expand Product section and go to Features as show below

  3. When you scroll to the very bottom, you’ll find Data Validation option turned out by default.

  4. Turn it on and Save the Settings.

  5. Also, in the App Designer for Model Driven Apps, click on Settings on the Editor. Click on Settings in the Command bar and then go to Upcoming features in the Settings list.
    You’ll find that the Enable Smart Email Address Validation Control feature is still set to No.

  6. Turn this feature on, Save the settings and Publish the App again before running it.



Validation in D365 Sales Example

Let’s look at the below example –

  1. When you have enabled the Email address validation, you can try to enter the below data which is invalid on purpose and see the result.
    When you enter an address, it’s validating on the fly.


  2. It’ll show that the domain is known but disposable, for example.

What Validation is considered?

Below are the validations that are carried out –

  1. Incorrect Syntax – Like Email Domain and Username can’t exist together
  2. Disposable Domain – Temporary Email domains.
  3. Test or spam emails – You can turn this feature off is you are testing in Sandbox and enable for Production to prevent spam emails being entered.
  4. Expired Email Addresses – Disabled emails which can’t send or receive Emails.
  5. Emails that bounce back – Like disabled addresses which bounce back

Here’s Microsoft official documentation for this feature – https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-validation-email-column?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Install correct .NET Framework for Dynamics 365 CRM Plugin Assembly | Plugin Registration Tool

Here’s how to solve if you see the below error while updating/registering your Plugin assembly in Plugin Registration Toolbox

Here’s how to go about solving the same!

Error while Updating Plugin Assembly

In case you see the above error in Plugin Registration Toolbox, here’s how you can upgrade your Project in Visual Studio to compile using the correct .NET Framework version as suggested in the error –

  1. Go to Properties of the Project and look for Application tab

  2. Now, drop down on the Target Framework and look for the version asked as in the error. At times, it appears that you don’t have it installed on the machine given that you just changed your system, so you need to download it.

    Select “Install other frameworks…”

  3. You’ll be redirected to this page (unless there’s a change in the future) – https://dotnet.microsoft.com/en-us/download/visual-studio-sdks?cid=getdotnetsdk
    And you can find the right Framework once you look for it. In this case, I need 4.7.1 version.

  4. Save the file and install once download.

  5. Once you begin to install, it’ll go about the same way as any other installer.


    And you’ll see this will be installed quickly [within few moments]

  6. Once done, close and restart Visual Studio and then again check the Applications section in Project’s Properties.
    You’ll see the installed version appear there.

  7. And once you select it, it’ll ask before applying this framework.


  8. Click Yes and compile the Assembly again. Once done, you’ll be able to register your plugin on the Plugin Registration Tool successfully.

Hope this helps!

Thank you!