Data Model
The Data Model section covers the AOT objects responsible for defining how data is structured, stored, retrieved, and consumed in Dynamics 365 Finance & Operations. These objects form the foundation of the application — every form, report, data entity, and integration ultimately reads from or writes to objects in this layer.
Tables
A Table represents a physical database table. Tables define the persistent data model: columns (fields), unique and non-unique indexes, foreign-key relations, field groups for UI layouts, and validation/event logic via overridable methods. Every record operation — select, insert, update, delete — passes through the table buffer.
Sub-pages: Fields · Field Groups · Indexes · Full-Text Indexes · Relations · Code Examples
Views
A View is a virtual, read-only table backed by a SQL CREATE VIEW statement. Views encapsulate complex query logic — joins, filters, aggregations, computed columns — and expose the result set as if it were a table. They are consumed by forms, reports, data entities, and other queries with standard select syntax.
Sub-pages: Fields · Field Groups · Indexes · Relations · Metadata
Queries
A Query is a reusable, declarative data retrieval definition. Queries specify which tables to read, how to join them, what ranges to apply, and in what order to return results. They can be referenced by views, forms, reports, and data entities, or built and executed dynamically in X++ code.
Sub-pages: Query Extensions
Extensions
| Extension Type | Description |
|---|---|
| Table Extensions | Add fields, indexes, relations, and event handlers to existing tables |
| View Extensions | Add fields and modify data sources on existing views |
| Query Extensions | Add data sources and ranges to existing queries |