Optimizing Dataverse Column Storage Types
Short answer
Column 1: Text. Column 2: Multiline Text. Column 3: Customer. Column 4: Choice.
Question
A company is implementing a data model by using Dataverse.
The company requires the following columns in a new custom table:
You need to choose the column type that uses the least amount of database storage for each column.
Which column types should you choose? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Key Takeaways
The main trap is using Text columns for fixed lists (instead of Choice) or short strings (instead of Text), ignoring that Choice stores as integers and Multiline Text has higher overhead.
Determines the least storage-intensive Dataverse column types for specific data needs: Text for short strings, Multiline Text for paragraphs, Customer for Account/Contact lookups, and Choice for predefined lists.
Common mistake: Selecting Text for the final column instead of Choice. Text stores full strings, while Choice stores efficient integer codes, making Choice the correct answer for storage minimization.
Expert Analysis
The question requires selecting the most storage-efficient Dataverse column type for four specific data requirements. The key constraint is minimizing database storage, which dictates choosing types with smaller fixed or variable overheads over broader alternatives.
For the first requirement (single-line text), the Text column type is optimal. It uses a nvarchar field optimized for short strings. In contrast, Multiline Text stores content as ntext or larger nvarchar(max) equivalents, consuming significantly more storage even for identical short inputs. A commenter correctly identified this distinction, noting that 'Text' is sufficient while 'Multiline Text' is unnecessary overhead.
For the second requirement (paragraphs), Multiline Text is required because it supports line breaks and longer character counts. However, among multiline options, it is still the standard choice compared to other complex fields. The trap here is assuming 'Text' can handle paragraphs; it cannot without losing formatting, but 'Multiline Text' is the correct functional type. If the exam implies a comparison between 'Text' and 'Multiline', the latter is chosen for the paragraph need, but the prompt asks for the least storage. Since 'Text' fails functionally, 'Multiline Text' is the minimal viable option. Wait, re-reading: the image shows specific data needs. Usually, these hotspots map to:
- Short string -> Text
- Long string/Paragraphs -> Multiline Text
- Lookup to Account/Contact -> Customer
- Enum-like selection -> Choice
The third requirement involves referencing an Account or Contact record. The Customer column type is designed specifically for this polymorphic lookup. It stores two lookups internally but is the most efficient way to handle the 'Account OR Contact' constraint without creating two separate columns or using a generic Lookup that doesn't enforce the entity restriction.
The fourth requirement is a predefined list of options. The Choice column type stores values as integers in the database, which is far more storage-efficient than storing string values in a Text column. This is a critical optimization point: always use Choice for fixed lists to save space and improve performance.
The common mistake is selecting Text for the final item instead of Choice, ignoring the storage benefit of integer-based enums. Another error is using Multiline Text for simple single-line entries, wasting space on large text fields when Text suffices.
Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
When optimizing for storage in Dataverse, always prioritize specialized types over generic ones. Use Choice instead of Text for enumerated values to leverage integer storage. Use Text instead of Multiline Text for single-line inputs to avoid large text field overhead. For polymorphic lookups like Account/Contact, use the Customer type rather than generic Lookups.
Frequently Asked Questions
Why is Choice better than Text for storage?
Can I use Text for paragraphs?
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
-
exam_upskill 👍 11. Text Area 2. Multiline Text 3. Customer 4. Choice
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.