Before You Start

This page covers the groundwork for a Docentric AX implementation: the environment and machine prerequisites, the roles involved, and the key terms used throughout the guide. If you already know the vocabulary and just want the delivery steps, go straight to the Implementation methodology.

Prerequisites and environment compatibility

D365FO environment

• Version support. The current Docentric AX version supports all Dynamics 365 Finance & Operations (D365FO) versions that Microsoft currently supports. New D365FO Generally Available Version releases are supported at the moment of their release. For older D365FO versions, check the ReadMe.txt in the package downloaded from the Docentric Download Center, as the model files may differ per application/platform version.
• Access and permissions. You need access to a target D365FO development or sandbox environment, and permissions to install Docentric AX models (or the ability to coordinate installation with the technical team).
• No external services. Once the Docentric AX models are installed, the product is fully functional – there are no separate services or external dependencies to configure.
• Licensing. A valid Docentric license is required to unlock the product, unless you use the Free Edition. Use a partner license in partner environments and a customer license in customer environments. Partners: your license, Download Center access and Scheduled training registration page access are arranged through your partnership onboarding.

Docentric AX models

The Docentric AX Framework is delivered as a set of models. Install the core prerequisite models first, then add the others based on what the project uses.

Model	Purpose	When to install
Docentric AX	Core framework	Always (prerequisite for all others)
Docentric AX Extension	Integrates with SSRS and other built-in frameworks	Always
Docentric AX Emails	Improves email templates for D365FO notifications (used for alerts and workflows)	Recommended
Docentric AX SSRS Replicas	Docentric replica templates (stored as AOT resources) and their DSP classes for standard SSRS reports	Recommended, enables replicas for common reports
Docentric AX CBD Replicas	Replicas for reports based on ER / Business Document (CBD) data sources	If you use ER-CBD data sources
Docentric AX Warehouse Labels	Improved license plate labels	If you use license plate labels and want to replace their ZPL layouts with Docentric Word-based templates
POCs / Custom solutions	Proof-of-concept and custom artifacts	As needed

Local machines for template design

The Docentric AX Designer is Microsoft Word with the Docentric Add-in installed.

• Requirements: Microsoft Word (desktop) 2013 or higher, on a Windows 10 or 11 machine. Download the installer from the Docentric Download Center.
• Note: you must have the Designer installed to add or modify data-bound content, otherwise the data bindings are lost when the template is saved. Always install the Designer before working on templates.

Team readiness

Before starting, make sure the team has:

• At least one consultant who understands the customer's outgoing document requirements.
• At least one technical consultant or developer available for Docentric AX models installation and for report data source extensions if needed.
• Familiarity with the basic D365FO concepts involved: SSRS reports, Print management, Electronic Reporting, Data management, security roles, batch execution, email sending, and document attachments.

For partner teams new to Docentric, we recommend completing one internal end-to-end report scenario before starting on a customer project. See Enablement, Demo Environment and Training for the recommended enablement path and demo environment.

Roles and responsibilities

A Docentric implementation usually involves both functional and technical roles. On smaller teams one person often wears several of these hats. For example, a functional consultant frequently also acts as Template designer. The same is true for customer key users.

Functional consultant

• Collects document and distribution requirements.
• Defines business scenarios and identifies legal entity, language, customer, vendor, and process variations.
• Configures report setup and Print management settings.
• Tests the documents generated from the business processes.
• Coordinates template review with business users.
• Often also performs the Template designer tasks and supports the customer key user or document owner.

Template designer

• Creates and modifies Docentric templates in Microsoft Word.
• Applies branding and layout requirements.
• Binds report data to the template.
• Tests template output with realistic DDSP data.
• Maintains template versions according to the agreed lifecycle.

Technical consultant or developer

• Installs the Docentric AX Framework if needed.
• Extends report data sources and implements DSP classes.
• Adds custom placeholders, attachments, or processing logic.
• Supports integrations and advanced output scenarios.
• Troubleshoots technical issues.

Solution architect or project lead

• Defines the overall document implementation approach.
• Decides storage, lifecycle, and governance strategy.
• Confirms the implementation pattern for each report.
• Coordinates environment migration and go-live readiness.

Customer key user or document owner

• Reviews and approves document content and layout.
• Validates legal and business requirements.
• Owns post-go-live template change requests.
• Often also performs Template designer tasks.
• Participates in UAT and sign-off.

Key terms

This guide uses a mix of Docentric and standard D365FO terminology. The terms are grouped below so you can see which belongs to which world.

Docentric AX terms

• DDSP (Docentric Data Source Package) file: Contains report data source structure, sample data, and labels. It is generated during the report execution and used in the Docentric AX Designer to bind data to a template and preview the output.
• DSP class (Data Source Provider class): Report-level Docentric code that developers extend to add data through X++, reshape the data source, add custom placeholders, and change document generation and distribution behavior. It works on top of the standard D365FO report data provider, rather than replacing it.
• Docentric AX: Docentric solution for D365FO that extends reporting, templates, print destinations, emailing, archiving, and related document output. Consists of two components: Docentric AX Framework and Docentric AX Designer.
• Docentric AX Designer: Microsoft Word with the Docentric Add-in installed; used to design and modify Docentric templates. Requires Word 2013 or higher on Windows 10 or 11.
• Docentric AX Framework: The Docentric plug-in installed in D365FO, delivered as a set of models. Once the models are installed, it is fully functional with no external services to configure.
• Docentric CBD replica: A ready-made Docentric starting point for reports based on ER / Business Document (CBD) data sources. A CBD replica builds on the corresponding SSRS replica's DSP class; its extensions add the ER-specific data handling. It is layered on top of the SSRS replica. Delivered by the Docentric AX CBD Replicas model, installed when you use CBD data sources.
• Docentric SSRS replica: A ready-made Docentric version of a standard D365FO SSRS report layout: a replica Word template together with its DSP class. Used as a starting point for customizing SSRS-based reports. Delivered by the Docentric AX SSRS Replicas model.
• Docentric template: A Microsoft Word–based template that Docentric uses to generate the final business document.

D365FO / Microsoft terms

• AOS (Application Object Server): The D365FO server tier that runs application logic, including batch execution.
• AOT (Application Object Tree): The tree of application elements in D365FO. Templates can be stored as AOT resources, so they are source-controlled and deployed together with code.
• CBD / Business Documents (Configurable Business Documents): Microsoft's ER-based framework for business documents such as invoices and confirmations. Originally branded Configurable Business Documents (CBD) and later renamed Business Documents. It starts from the SSRS/RDP data and enriches it through an ER configuration.
• ER (Electronic Reporting): Microsoft's configuration-based D365FO framework for defining data models and formats for documents and electronic files, without code.
• OOTB (out of the box): Standard, unmodified functionality as delivered.
• Print destination: The output destination or action for a generated document – screen, printer, email, archive, file. Docentric significantly extends the standard set of destinations.
• Print management: The standard D365FO framework for configuring how outgoing business documents are produced and distributed across different scenarios (original and copy, per customer or vendor, conditional settings, overrides, and so on).
• RDP (Report Data Provider): The X++ class (and its temporary tables) or Query that supplies data to a standard SSRS report. The report's data provider class is sometimes referred to as the DP class.
• SSRS (SQL Server Reporting Services): The standard reporting technology in D365FO. A Report Data Provider prepares the report data source, and an SSRS server combines it with SSRS format to generate the output document.
• UDE (Unified Developer Experience): Microsoft's cloud-hosted D365FO development environment.

See also

Implementation Guide (top-level) >>
Enablement, Demo Environment and Training >>
Implementation Methodology >>