Data Types for Dynamics 365 Finance and Dataverse Virtual Tables
Short answer
CDE Use Long, GUID, and Real data types to ensure a strict 1:1 field count between the Finance entity and the Dataverse virtual table.
Question
The company requires that you integrate the Finance environment with a Power Platform environment.
You plan to integrate the Finance entity in Dataverse by using a Dataverse virtual table. You add the fields with specific data types to the entity.
You need to ensure that the total number of fields are the same in both the Finance entity and the virtual table.
Which three data types should you use? Each correct answer presents part of the solution. (Choose three.)
NOTE: Each correct selection is worth one point.
Key Takeaways
The question tests the understanding of Dataverse virtual table schema constraints, specifically that only primitive scalar types map directly to single columns, whereas enums and containers require multiple or unsupported structures.
This page explains which three data types support a strict 1:1 field mapping between Dynamics 365 Finance entities and Dataverse virtual tables. It clarifies why container and enum types are excluded from this specific integration requirement.
Common mistake: Learners often select Enum types because they are common in Finance, failing to realize that Enums generate two columns (value and label) in Dataverse, violating the 'same total number of fields' rule.
Expert Analysis
Why the Answer Is Correct
To ensure the total number of fields is identical between the Finance entity and the Dataverse virtual table, you must use primitive scalar data types that map one-to-one. In Dataverse virtual tables, GUID, Long (Int64), and Real (Decimal) are supported primitive types that each occupy exactly one column. Therefore, selecting Long, GUID, and Real ensures a direct 1:1 correspondence.
Why the Other Options Are Wrong
Container types are generally not supported as direct columns in standard virtual table schemas for simple 1:1 mapping scenarios due to their complex structure. Enum types in Dataverse typically expand into two columns: one for the integer value and one for the string label. This expansion means an Enum field in Finance would result in two fields in the virtual table, breaking the equality constraint specified in the question.
Community Comment Notes
Community feedback highlights that primitive scalars like GUID, Int64/Long, and Real map strictly 1:1 to single Dataverse columns. As noted by users in the comments, Enums generate two columns (a value and a label column), and Container types are unsupported for this specific mapping requirement.
Exam Strategy
When integrating with Dataverse virtual tables, always prioritize primitive scalar types (String, Int64, Decimal, Guid) for direct field mapping. Be wary of complex types like Enums or Containers, as they often require additional handling or do not map 1:1.
Frequently Asked Questions
Why can't I use Enum types for this integration?
Are Container types supported in Dataverse virtual tables?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
AbhiN1106 👍 1In Dataverse virtual entities, primitive scalar types like GUID, Int64/Long, and Real/Decimal map strictly 1:1 to a single Dataverse column. Enums generate two columns (a value and a label column), and Container types are unsupported.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All MB-500 Questions
Access 115 questions with complete answers and detailed explanations.
View Full MB-500 Practice Test →