Microsoft Dynamics 365 Customer Experience Analyst : Create or modify fields

In Microsoft Dataverse, creating or modifying fields allows you to tailor data tables to meet your organization’s specific business needs. Fields (also called columns) define the type of data that can be stored, such as text, numbers, dates, choices, or lookups to other tables. When creating a new field, you can configure properties like the data type, display name, logical name, and whether it is required. Modifying an existing field lets you adjust attributes such as labels, descriptions, or field behavior without affecting stored data. However, some properties, like the data type, cannot be changed once the field is created. By customizing fields in Dataverse, you can ensure that your applications capture, validate, and display information in a structured and meaningful way, supporting better data consistency and business processes across Dynamics 365 and Power Platform solutions.

In Dataverse, a field (also called a column) is the schema definition of a data attribute stored within a table. Each field is defined by metadata, which includes properties such as Display Name, Logical Name, Data Type, Requirement Level, and Behavior.

1. Creating Fields

When creating a field, you define:

• Data Type: Determines the kind of data the field can hold (e.g., Single line of text, Whole number, Decimal, DateTime, Boolean, Choice, Lookup, Currency, File, Image).
• Format: Some data types allow formats (e.g., Text can be Email, URL, Phone).
• Requirement Level: Specifies if the field is Optional, Business Recommended, or Business Required.
• Search & Indexing: Fields can be configured to be searchable and included in Dataverse search indexing.
• Advanced Options: Includes enabling auditing, security, and field-level security.

Technically, a new field creates a column in the underlying SQL Azure database that supports the Dataverse environment.

2. Modifying Fields

• You can modify certain properties after creation, such as Display Name, Description, Requirement Level, and Behavior (e.g., Calculated, Rollup).
• Immutable properties like Data Type and Logical Name cannot be changed once created because they directly map to the SQL schema.
• If business rules change, admins can deactivate or hide a field instead of deleting it, since deletion can have dependencies (views, forms, business rules, workflows, plugins, or Power Automate flows)

3. Special Field Types

• Calculated Fields: Perform real-time calculations based on other fields using logical expressions.
• Rollup Fields: Aggregate values (e.g., SUM, COUNT, MAX, MIN) from related child records.
• Lookup Fields: Create relationships between tables by referencing another table’s record.

4. Best Practices

• Always define meaningful logical names (used in backend code and Power Fx formulas).
• Use field security profiles for sensitive data.
• Test calculated and rollup fields for performance impact.
• Use solutions for deployment across environments (dev → test → prod).

In summary: Creating or modifying fields in Dataverse involves defining metadata at the schema level, which directly influences storage, relationships, and behavior across Dynamics 365 and Power Platform apps.