Dual-write and Virtual Tables


  • These is a feature provided for interaction between Dataverse and Dynamics 365 Finance and Operations application.
  • Provides bidirectional integration between Finance and Operation apps and Dataverse
  • Whenever a user makes any change in Finance and Operation apps, it causes writes to Dataverse and vice-versa.
  • Should be used when you are working with Dynamics 365 apps
  • These used in scenarios where near real-time integration is required.
  • Dual-write will duplicate the data in both the directions (to and from Dataverse)

Virtual Tables

  • Used for data from external systems
  • Replication of data does not happen
  • Custom coding is not required
  • In-built or Custom connectors can be used to access data from external systems

Types of tables in Dataverse

There are four types of tables in Dataverse:

  • Standard: These are the pre-built set of tables that are included in every instance of Dataverse database. You can change name of these tables and columns of these tables, but you cannot delete any column from these tables. These are the generic tables that can be used across any organization. You can customize them as per your requirement. It is recommended to try to use these tables before creating new custom tables.
  • Complex: These tables contain complex and server-side business logic, including workflows and plugins. Users need P2 or Dynamics 365 license to work on these tables. Care should be taken while working on these tables as they include server-side logic.
  • Restricted: These tables are linked to Dynamics 356 applications for which each user should have the license for that Dynamic 365 application to perform CRUD (Create, Read, Update and Delete) operations.
  • Custom: These are the tables that are created for a specific business requirement.

Create New Environment

Whenever a user signs up for Power Apps or Dynamics, a new environment is automatically created. This environment will be the default environment.

Below are the steps to create a new environment:

Read More »

Compare two Strings without matching case

Below is the code I used to compare string values from two Text Inputs. This will not compare the case.

That is, “Apple” will be equal to “apple”.

         StartsWith(TextBox1.Text, TextBox2.Text),
         "values matched", "Values did not matched"