Improve Dataverse Choice Columns Before Loading Access Data
Diesen Beitrag auf Deutsch lesen
Review transformed Access data, improve the Dataverse model, and choose local or global Choice columns before importing.
TL;DR
Before loading transformed Microsoft Access data into Dataverse, review the data model and replace repeated text values with Choice columns where appropriate. Local choices belong to one table, while global choices are created in solutions and can be reused by tables across the environment. The choice depends on whether reuse is needed.
Original by Charles, on charleslakes.com. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Audit transformed Access data before import and consider Choice columns for repeated values, because controlled options can reduce inconsistent entries.
- Admins/IT: Decide whether each Choice should be local or global based on reuse, because global choices can be used by multiple tables in the environment.
Frequently asked questions
How can Choice columns improve imported Access data in Dataverse?
Choice columns replace repeated free text values with defined options, helping reduce inconsistent entries during Dataverse data loading.
What is the difference between local and global choices in Dataverse?
Local choices belong to one table, while global choices are created in solutions and can be used by tables across the environment.
When should I use a global Choice in Dataverse?
Use a global Choice when the same set of options is needed by multiple tables in the environment.