Microsoft Dynamics 365 Finance and Operations Developer — Lesson 2: Data Models, Tables, Queries and Data Entities

Learning Objectives

• Create and extend tables, fields, indexes, relations, enums, views, queries, and data models
• Build data entities, imports, exports, mappings, validation, staging, and migration workflows
• Validate data models, tables, queries and data entities decisions with documented requirements, test evidence, risk controls, and measurable acceptance criteria

Detailed Topics

• Create and extend tables: Create and extend tables, fields, indexes, relations, enums, views, queries, and data models
• Build data entities: Build data entities, imports, exports, mappings, validation, staging, and migration workflows
• Validate data models: Validate data models, tables, queries and data entities decisions with documented requirements, test evidence, risk controls, and measurable acceptance criteria

Guided Demonstration

1. Review the requirement, users, data, dependencies, permissions, risks, and expected result.
2. Demonstrate the relevant design, configuration, development, analysis, administration, or support workflow step by step.
3. Capture settings, outputs, logs, screenshots, calculations, test results, and other useful evidence.
4. Compare the observed result with acceptance criteria and explain any corrective action.

Hands-On Activity

Develop and validate a data model and entity.

• Document assumptions, prerequisites, and the planned sequence before starting.
• Complete the activity and preserve evidence of normal, boundary, and failure behavior.
• Record issues, corrective actions, reusable notes, and the next improvement priority.

Scenario Analysis

• Identify the business or technical decision that must be made.
• Compare valid implementation approaches and their trade-offs.
• Consider security, privacy, accessibility, performance, support, and operational impact.

Troubleshooting Focus

• Separate symptoms from causes and collect evidence before applying a fix.
• Check configuration, data, permissions, dependencies, capacity, connectivity, and recent changes.
• Validate rollback, recovery, ownership, user impact, and business continuity.

Validation Checklist

• The requirement, scope, inputs, and expected outcome are clear.
• The selected design or configuration is documented and follows approved standards.
• Normal, boundary, failure, security, accessibility, and operational conditions are reviewed.
• The result is supported by evidence and the next improvement is prioritized.

Lesson Outcome

Learners can explain and apply Data Models, Tables, Queries and Data Entities in a realistic scenario and validate the result with documented evidence.