Data management package REST API

This article provides an overview of the Data Management Framework (DMF) package REST API in Dynamics 365 Finance & Operations. This API facilitates programmatic interaction with data management tasks such as data import/export through a unified interface using packages.

Summary

The Data Management Framework package REST API enables automation and integration scenarios by exposing endpoints for:

• Managing data packages that contain multiple data entities
• Initiating execution of data import or export operations
• Monitoring status and retrieving results of data jobs
• Managing recurring integration processes at key decision points

The API is designed to support complex data management use cases with a scalable, RESTful service interface.

Key Concepts

• Package: A collection of data entities and related settings grouped for import/export.
• Job: Execution instance of a data management operation against a package.
• Recurring integration APIs: Specialized REST endpoints that enable integration at logical decision points during data processing.

Recurring Integration APIs Overview

The article provides a detailed table outlining recurring integration APIs available for various decision points in the Data Management Framework:

These endpoints enable custom business logic triggers during the data management process.

Usage Highlights

• The APIs accept and return JSON payloads.
• They support asynchronous job execution with status tracking.
• Useful for data integrations requiring periodic data sync or batch processing.
• Enable DevOps and automation scenarios (CI/CD for data packages).
• Can be called from external systems or custom scripts.

Reference Links

• Original Article on Microsoft Learn
• GitHub source: Data Management API Documentation

This API is a core integration point for Finance & Operations developers and technical consultants implementing automated data import/export workflows within Dynamics 365.

Role-based security

This article describes the fundamental elements of role-based security in Dynamics 365 Finance & Operations. It covers the concepts and components used to manage security access in the system, including security roles, duties, privileges, and permissions.

Key Concepts

• Security Roles: High-level containers representing a job function or responsibility in the organization. Roles aggregate multiple duties.
• Duties: Groupings of privileges that represent specific business tasks or responsibilities. Duties are assigned to roles.
• Privileges: Fine-grained access rights that control the ability to perform specific operations, typically at the data level.
• Permissions: The actual rights granted to perform operations on objects (such as tables or forms) in the system. Permissions are assigned to privileges.

How Role-Based Security Works

• Users are assigned one or more security roles.
• Each role includes several duties.
• Duties include multiple privileges.
• Privileges define permissions to perform particular actions on data or application objects.
• This hierarchical structure ensures that users receive only the access necessary to perform their job functions, following the principle of least privilege.

Benefits

• Granular control over system access.
• Simplified management by grouping permissions into privileges and duties.
• Flexibility to customize roles for different organizational needs.
• Enhanced security compliance by enforcing least privilege access.

Summary Table of Security Model Elements

Reference: Role-based security - Finance & Operations | Dynamics 365

Row version change tracking for tables and data entities

This article explains how to enable row version change tracking for tables and data entities in Dynamics 365 Finance and Operations apps. Row version change tracking helps detect and manage data changes efficiently, useful in integrations and data synchronization scenarios.

Overview

• Row version change tracking identifies changes (updates, inserts, deletes) in table data using row version IDs (typically a timestamp or version number).
• It is applicable to both tables and data entities in Finance and Operations apps.
• Enables incremental data synchronization and event processing by tracking row-level changes.
• Supports detecting changes since a given version or timestamp.
• Requires configuration both on the table and data entity layers.
• There are specific rules and constraints on which tables and entities support change tracking.

How to enable row version change tracking

For tables:

1. Open the Table design in Visual Studio within your Finance and Operations development workspace.
2. Set the Change tracking property of the table to enable row version tracking.
3. Define or confirm the RowVersion field on the table, typically a timestamp or version number column.
4. Build and deploy your application changes.

For data entities:

1. Open the Data entity in Visual Studio.
2. Set the Change tracking enabled property to Yes for the data entity.
3. Map the row version field from the underlying table to the entity if needed.
4. Build and deploy the updated data entity.

Important considerations and rules

Summary

Enabling row version change tracking in Dynamics 365 Finance and Operations:

• Enhances data integration by allowing incremental data retrieval.
• Requires configuration on both tables and data entities.
• Depends on the presence and correctness of the row version field.
• Should be managed carefully to balance performance and accuracy.

For developers and IT professionals working on integrations, data entities, or customizations, this feature provides a reliable change detection mechanism supporting efficient data movement and event handling.

Original article link:
Row version change tracking for tables and data entities - Finance & Operations | Dynamics 365

Service endpoints overview

This article provides an overview of service endpoints available in Dynamics 365 Finance & Operations (D365 F&O), explaining how they enable integration and interaction with external systems via data entities. It includes a summary of key service endpoints and the services they expose.

Key points

• Service endpoints are integration points in D365 F&O that expose business logic and data entities as endpoints accessible externally.
• They facilitate operations such as data retrieval, data submission, and business process invocation.
• Service endpoints support different communication protocols and authentication methods aligned with the platform’s security.
• Various service endpoints provide access to different sets of services tailored for specific integration needs.

Table of available service endpoints and associated services

Usage scenarios

• Automating data imports or exports using the Data management REST API.
• Extending business functionality through custom service endpoints.
• Integrating legacy systems using SOAP endpoints.
• Reporting and analytics via Entity store access.

Additional information

• Authentication methods include Azure Active Directory OAuth tokens and other Microsoft identity platform protocols.
• Service endpoints are versioned and aligned with Dynamics 365 updates to ensure compatibility.
• Developers can use Visual Studio and Lifecycle Services (LCS) to deploy and manage these service endpoints.

For detailed configuration steps, permissions, and examples of using each type of service endpoint, refer to the official documentation linked below.

Original article: Service endpoints overview - Finance & Operations | Dynamics 365

Security Architecture

This article provides an overview of the security architecture for Dynamics 365 Finance and Operations, covering key areas such as authentication, authorization, data security, and auditing of user logins.

Key Components of Security Architecture

• Authentication

  • Uses Azure Active Directory (Azure AD) for identity verification.
  • Supports Single Sign-On (SSO) capabilities.
  • Ensures only authorized users can access the system.

• Authorization

  • Based on role-based security model.
  • Users are assigned security roles that define permissions.
  • Permissions govern access to data and functional areas within Finance and Operations.

• Data Security

  • Implements layered data access restrictions.
  • Ensures users can only read, create, update, or delete data based on their assigned permissions.
  • Field-level security further controls access to sensitive data elements.

• Auditing and Logging

  • Tracks user login sessions and activities.
  • Helps in compliance and forensic analysis by recording user actions.
  • Supports audit trail creation for security governance.

Summary

Dynamics 365 Finance and Operations uses a comprehensive security framework combining Azure AD authentication with role-based authorization. Data access is tightly controlled at multiple levels to safeguard organizational information. Audit capabilities provide transparency and accountability for user activities.

For more details, see the full article:
Security architecture - Finance & Operations | Microsoft Learn