LEGEND
Yes
Partially
No
Free Edition
On Roadmap
SSRS Enabled

Feature List

The complete list of Docentric Free and Full Edition features
compared with Configurable Business Documents and SSRS Reports for better understanding.

Expand allExpand all Collapse allCollapse all


FEATURE CBD SSRS DOCENTRIC
Designer
Designing in Word or Excel yes

Templates are static Excel documents without data binding between data models and their dynamic parts but via named ranges and cells in D365FO’s ER Format designer. Consequently, user cannot easily shift, add or remove data bound to Excel cells in a template. See gallery >>

Templates are designed in Word using built-in Content Controls and Custom XML parts, a limited technology, non-robust and extremely non-user friendly. See gallery >>

no

SSRS Report Designer is a developer tool hard to comprehend, where each design change is time-consuming and costly.

yes

Templates are designed in Word using Docentric Designer. True user-friendliness and great design capabilities.

See gallery >>

See the comparison between CBD, SSRS and Docentric Designer >>

Preview option no

User has to start the report from D365FO to see the design changes.

no

User has to compile, deploy and start the report from D365FO to see the design changes.

yes

  • Preview at any design step to see the results – this is a huge time saver.
  • Change sample data to test different scenarios, e.g. to conditionally show or hide the Discount column.
  • Preview a template in different languages.
Updating templates without deployments yes no yes
Template storage
Azure storage or SharePoint yes

Attachments (Azure Blob storage / SharePoint)

no

AOT

yes

AOT / Azure Blob storage / SharePoint / File system

Learn more >>

Setup inside D365FO yes

Flat structure; templates can be filtered per functional area.

no yes

  • Structured per report and report groups.
  • Multiple templates per report, company and language, which can be selected directly on the Print destination settings form.
  • The concept of default template per report.
Versioning yes

Supported via ER 'Business Document Management'.

yes

Supported via Azure DevOps.

yes

Supported via SharePoint / Azure DevOps.

General
Integration with Print management SSRS reports yes

CBD sit on top of SSRS reports and cannot be printed outside the SSRS report execution pipeline, since SSRS is responsible for preparing report data.

CBD are integrated only with Print management SSRS reports, because their execution is triggered by selecting an ER Format as the target Report format in Print management setup. However, instead of using Print management destinations, for printing ER Formats are always used ER destinations.

yes yes

Docentric sits on top of SSRS reports, replacing SSRS report designs with Docentric templates and distributing generated reports to improved Docentric print destinations. Docentric templates are designed in MS Word and can be published without deployments. Report menu items and security are inherited from SSRS.

Additionally, any SSRS report can be printed using improved Docentric print destinations, which is basically the essence of Docentric Free Edition.

Integration with other SSRS reports no

CBD are not integrated with Non-Print management reports.

However, any SSRS report can be converted to a CBD report but without ER Format, so the original report can be printed using a Docentric template and improved print destinations. This way end-users can design SSRS reports with Docentric Designer and add additional report data using ER Data models. Learn more >>

yes yes

Docentric supports all SSRS reports no matter if they are Print management reports or not. It is seamlessly integrated with SSRS print destinations, Print management and business processes resulting in posting and printing documents.

Any SSRS report design can easily be converted into a Docentric template, without help of developers.

Integration with CBD reports yes no partially

Docentric utilizes the best part of CBD, which is using ER Data models as report data sources. This way end-users and functional consultants can add additional data to reports, without help from developers. Reports are still designed with Docentric Designer and distributed via improved Docentric print destinations.

Learn more >>

Integration with other ER reports no no no

On the roadmap to support printing Docentric designs based on Non-CBD ER Data models using improved Docentric print destinations.

Provided reports OTTB yes

34 core documents, 64 localized documents.

yes

Cca. 1000 reports.

yes

For common reports, Docentric provides both SSRS and CBD Replicas (40+ reports).

See the complete report list >>

Custom reports yes

Only custom Non-CBD ER reports can be created. Learn more >>

yes yes

Report execution log inside D365FO yes

Supported via ER jobs, which contain only basic info such as filename and username.

no no

Advanced setup for report execution database logging, e.g. per report, company, print destination, failure/success. Advanced search by report metadata and clean-up.

Diagnostics inside D365FO no

Diagnostics is done via Event log and Application Insights, which are not accessible from within D365FO. You must contact Microsoft Support to access diagnostic data for cloud non-dev environments.

no

The same as for CBD.

partially

  • Print reports with system information such as installed fonts, environment flags, etc.
  • Trace report execution times and events in the database (document generation and distribution).
  • Dump templates and runtime DDSPs to the browser or database.
  • Dump EMF files (printing documents) and EML files (outgoing emails) to the browser or database.
Moving reports between environments without deployment yes

Export/Import tools for ER configurations.

no yes

Export/Import tools and Data Entities.

Learn more >>

Documentation and tutorials partially no yes

Data sources
Adding additional data by end-users yes

Non-user friendly and requires deep understanding of database relations. Costly to debug when an issue appears (e.g., why a newly added field is not populated).

no yes

Docentric supports this feature by reusing ER Data models and Model mappings. In other words, a user is able to select the ER configuration on Docentric report setup as a data source for a particular report, e.g. Customer invoice.

Learn more >>

Adding additional data by developers yes yes yes

Developers can add additional data using the cost-effective Docentric approach without extensions and without changing report data source tables or queries. Learn more >>

Custom fields included automatically no no yes

Custom fields, if defined by end-users, will appear automatically in report data sources.

SSRS data sources yes yes yes
ER Data models yes no yes

Multilingual capabilities
Multilingual reports yes yes yes

  • Reusing D365FO labels.
  • Reusing labels from ER Data models.
  • Ad-hoc creation of User-defined labels.

Learn more >>

Multilingual print settings no no yes

Use D365FO and Docentric User-defined labels in print settings such as Email body, subject, output filename, etc.
Learn more >>

Additionally, you can use multilingual Email templates.

Adding new label translations by end-users yes no yes

Configurable report execution language yes

Language can be configured per Electronic reporting format. Only pre-installed D365FO languages are supported.

partially partially

Currently, report execution language is overtaken from underlaying SSRS reports, e.g. for invoices this is usually the customer language. Run-time language can be changed programmatically.

On the roadmap: Language can be configured per each report run – on the Print destination settings form, allowing selection of any language, not just pre-installed languages. In combination with User-defined labels, you can now cover ALL languages for Docentric report designs and print settings, including those which are not shipped with D365FO OOTB.

Document generation
Embedded in D365FO partially

Depends on Microsoft Office Cloud Service for conversion to PDF.

no

Uses SQL Reporting Services to generate documents.

yes

Docentric Report Engine is a component fully running inside D365FO. There is no external services or dependences. Zero installation and no additional virtual machines and maintainance.

PDF output format yes

Supported via Microsoft Office Cloud Service.

yes yes
Word output format yes

Supported for documents designed in Word.

partially

Supported Word binary file format (.doc) only.

yes
Excel output format yes

Supported for documents designed in Excel.

yes no

On the roadmap to support Excel as output format, and consequently to enable 'Export to Excel' from Docentric Viewer also for reports based on Docentric templates.

TIFF output format no yes yes

TIFF is a lossless image file format, which can contain multiple pages, e.g. of scanned documents. It can also be used for archiving.

Custom fonts no no yes

Missing or custom fonts can be added as AOT resources or uploaded on-the-fly from within D365FO.

Learn more >>

Barcodes partially

Supported through the Barcode ER data source type, which encodes any text into a barcode non-vector image for the selected barcode symbology.

partially

Implemented with barcode fonts.

yes

Embedding subdocuments / Attachments partially no yes

You can embed subdocuments in Word and HTML format programmatically or by using ER Data models as report data sources. Learn more >>

Additionally, you can use Form notes and Attachment notes as HTML subdocuments.

Merging documents / Attachments by developers no no yes

You can merge documents in Word or PDF format. The most common scenario is to append T&Cs or product specifications stored as Attachments to the main report. Learn more >>

Merging documents / Attachments by end-users no no no

Form notes supporting HTML with placeholders no no no

In addition to plain text, HTML is supported for Form notes, which are used as dynamic parts of designs for most common reports. HTML is configured using a rich HTML editor with report-specific placeholders.

Attachment notes supporting HTML no no no

In addition to plain text, HTML is supported for Attachments of type Note. HTML is configured using a rich HTML editor. Notes are already part of the data source for many reports.

PDF Encryption no no yes

Protect outgoing PDF documents with configurable passwords. You can make them dynamic by using placeholders (e.g. @CustomerVATNumber@).

Learn more >>

PDF Document properties no no yes

PDF document properties such as Author, Title, Subject and Keywords can be configured per report and company. You can make them dynamic and multilingual by using placeholders and labels (e.g. @SYS14204@ @InvoiceId@).

Learn more >>

On the roadmap is to support Custom document properties as well.

PDF Electronic signature no no yes

PDF documents can be digitally signed with X.509 certificates stored in Azure Key Vault or in the database in PFX format.

Learn more >>

Restrict printing, editing and copying parts of PDFs no no no

PDF/A no no no

PDF Attachments no no no

Print management
Integration with Print management partially

  • Print management setup is used only for ER Format selection, whereas configured print destinations are ignored. Instead, the ER destinations are used.
  • From 10.0.17, you can configure action-dependent ER destinations and use ‘Preview copy/original’ from Journals. Learn more >>
yes yes

Seamlessly & fully integrated with Print management.

See the comparison between CBD and Docentric integration with Print management >>

Print management preview no no yes

In addition to 'Preview copy/original' on journal forms, Docentric adds a new button 'Print management preview' to support report preview using the report design selected in Print management.

Print management data entity no no yes

Update Print management settings in bulk, or copy them between customers and environments.

Learn more >>

Print management utilities no no no

We already enabled access to Print management settings for all modules in one place.
Learn more >>

Besides, Print management utilities will enable users to:

  • View, filter and search Print management settings including setting overrides from within D365FO in a specialized form.
  • Update Print management settings in bulk without using Docentric Print Management Data Entity.
  • Locate and clean invalid Print management settings such as those which contain customer or vendor contacts/purposes with invalid email addresses.
Document distribution
Multiple selected print destinations yes partially

Via Print management.

partially

Via Print management but also as a new feature on the roadmap.

Multiple designs/templates per report yes

  • Adding new templates without coding.
  • Template selection per company but not per language.
yes

Only with coding.

yes

  • Adding new templates without coding.
  • Template selection per company and language.
Preview before print no no yes

Preview reports before emailing or printing.

Learn more >>

Placeholders in print settings partially

Supported for email print settings (To and Cc fields, Email body) and output filenames only.

partially

Limited to Email tokens, e.g. @@ and @Invoice@.

yes

Placeholders can be used in all print settings, e.g. email bodies, subjects, output filenames, names of target Azure containers or SharePoint folders.

Learn more >>

Placeholders provided OOTB no no yes

Via Docentric SSRS Replicas, which provides Custom placeholders OTTB.

Adding new placeholders by end-users yes

Supported, since any field from ER Data model can be used as a placeholder.

no yes

User-defined placeholders can be defined from within D365FO using the report data source and advanced formula editor.

Learn more >>

Integration with DocuSign no no no

Printing
Printing to network printers partially

  • Uses DRA and Adobe Acrobat.
  • Mass printing is not supported.
yes

  • Uses DRA to print to network printers.
  • Printing to local printers from SSRS PDF Viewer.
yes

  • Uses DRA to print to network printers.
  • Printing to local printers from Docentric Viewer.
Printing to local printers partially

Supported if the generated report is opened in Excel/Word app.

yes

Supported from SSRS PDF Viewer.

yes

Supported from Docentric Viewer.

Routing files to network folders partially

If DRA is running as a service, the PDF documents will automatically be routed to a preconfigured local network folder.

partially

Only if 'Print as PDF' is set via customization and DRA is running as a service. Otherwise Adobe Acrobat prints the report.

yes

  • Uses DRA to route PDF files from D365FO in the cloud to a preconfigured local network folder.
  • 'Print as PDF' option available on the Print destination settings form.

Learn more >>

User default printer no no yes

  • End-users can set up their default printer and use it when printing reports.
  • Administrator can configure default printers for all users.
  • Setup can be done per user, user group and company.

Learn more >>

User favorite printers no no yes

  • End-users can set up their favorite network printers, which makes printer selection easier when printing reports.
  • Administrator can set up favorite printers for all users.

Learn more >>

User allowed printers no no yes

  • Administrator can allow selection and use of particular network printers per user.
  • Setup can be done from both perspectives: per printer and per user, also with the help of security roles.
  • Users can print reports only to their allowed printers.

Learn more >>

Report restricted printers no no yes

  • Administrator can restrict the selection and use of particular network printers per report.
  • Setup can be done from both perspectives: per printer and per report.
  • Users can print a report only to printers allowed for this report.
  • Useful for checks, labels and other reports which should be printed to special printers only.

Learn more >>

Printing with custom fonts no no yes

Custom fonts are the fonts which are not pre-installed in D365FO environments. Printing Docentric reports that contain custom fonts to network printers is supported.

Learn more >>

Advanced printing features: Follow me, Using pre-defined printer trays, etc. no no no

On the roadmap to implement Docentric DRA. Learn more >>

Emailing
Email body partially

Plain text with placeholders.

no yes

  • End-users can use a rich HTML editor with placeholders (e.g. Invoice ID, Customer contact name) to edit Email body directly on the Print destination settings form.
  • Dynamic images (e.g. Company logo) are also supported. Learn more >>
  • (On the roadmap) Improved Email Body Editor with better templating capabilities to allow for conditional and repeating contents.
Use Email templates partially

Built-in Email templates with HTML body can be used as the email body, but in non-user friendly way, e.g. with %1, %2,… as placeholders.

no yes

Instead of editing Email body directly on the Print destination settings form, end-users can select pre-prepared Email templates.

Email templates are designed using the same rich HTML editor and placeholders, and can be configured per report and company but also per language. Furthermore, the template in the correct language will automatically be selected when emailing the report.

Learn more >>

Load from Email templates no no yes

Email body can be pre-loaded by selecting a particular Email template on the Print destination settings form and modified further if needed.

In this case, Email templates act as Email body snippets, i.e. as a snippet repository for different languages or email body parts.

Learn more >>

Open email before sending no no yes

End-users can edit outgoing emails with printed reports before sending.

Learn more >>

Multiple email sender accounts no no yes

  • Configurable ‘From’ for outgoing emails.
  • Use aliases or different email sender accounts.
  • Use third-party email providers.

Learn more >>

Email reports via Email distributor batch no no yes

Monitor and resend outgoing emails with printed reports using Batch email sending status.

Learn more >>

On the roadmap to support filtering outgoing emails when starting an Email distributor batch job (‘Records to include’). Additionally, users will be able to review and update ALL fields of email messages saved in Batch email sending status, including Recipients, Sender, Body, Subject, Attachments, etc.

Improved Email distributor batch no no yes

  • Filter Batch email sending status by new fields – Context information, Account and Document number, added and populated by Docentric for all report, workflow and alert emails.
  • Select which emails to send when configuring an Email distributor batch job (‘Records to include’).
  • Use Email distributor cleanup to delete or archive selected emails.
  • Review and update all fields of email messages saved in Batch email sending status, including Recipients, Sender, Body, Subject, Attachments, etc.
Bcc, Reply-to, Bounce-to and Message priority no no yes

Read and Delivery receipts no no yes

Additional email tokens no no yes

In addition to standard Print management email tokens Purpose and Primary contact, additional email tokens are introduced:

  • Order email,
  • Project email,
  • RFQ vendor email,
  • Delivery address purpose,
  • Delivery address primary contact.

Learn more >>

Printing redirections for unresolved email tokens no no yes

If the resolving of the used email tokens results in no email addresses, the printing will be redirected from Email to Printer, i.e. to the preconfigured print destination.

Learn more >>

Additional email attachments by end-users no no yes

Additional email attachments by developers no no yes

e-Invoice attachment no yes yes

Configurable error handling for report emailing no no no

End-users can configure how to handle invalid recipient addresses (To, Cc, Bcc) in case that email tokens or Docentric placeholders are used when emailing reports. They can choose between throwing an error, sending such emails out if possible, i.e. at least one recipient is valid, and applying Email token redirections.

Advanced reporting scenarios no no yes

Improved Exchange email provider no no no

Exchange email provider is improved to support embedded images and email signing.

Email signing and encryption no no no

Email templates for Workflow and Retail notifications no no yes

Edit email templates used for workflow and retail notifications using a rich HTML editor with placeholders, including dynamic images and tables. Attach context-related documents to outgoing emails.

Learn more >>

Improved Alert email notifications no no yes

When creating an alert rule, users can:

  • Select an email template for alert emails.
  • Choose whether to send alert emails synchronously or via Email distributor batch.
  • Use placeholders in alert email recipients: To, Cc, Bcc.
  • Attach alert-related documents to outgoing emails.

Users can edit email templates for alerts using a rich HTML editor with common and alert-rule specific placeholders.

Learn more >>

Saving to SharePoint, Azure and Attachments
Saving to SharePoint yes

Supported via Print archive and Power BI.

no yes

Saving to SharePoint On-Premises no no no

Saving to SharePoint with metadata fields no no yes

  • Reports can be saved to SharePoint document libraries with metadata fields such as Document ID, Account ID, etc.
  • Metadata fields can be used for document search, which also enables advanced scenarios for workflows and integrations.
  • Saving with metadata is triggered via Saving to SharePoint, Attachments and Print archive print options, if the target document library is configured so.
  • To map SharePoint document library columns with report metadata, common and report specific placeholders are used.

Learn more >>

Saving to OneDrive for Business no no partially

Saving to OneDrive for Business is supported via SharePoint UI and APIs. On the roadmap to create a dedicated UI for selecting a target location on OneDrive.

Saving to OneDrive no no no

Saving to Google Drive no no no

Saving to Azure Blob storage yes

Supported via Electronic Reporting Archive destination.

no yes

  • Save reports to a specified blob container and path on D365FO Azure Blob storage.
  • On the roadmap to enable selection of the output blob access tier (Account tier, Hot, Cool, or Archive) on the Print destination settings form.
Saving to Azure Files no

no no

Save reports to a specified Azure file share and folder path on D365FO Azure File storage.

Saving to Azure Data Lake Storage no

no no

Save reports to a specified file system and directory on D365FO Azure Data Lake Storage Gen2.

Saving to external Azure storage no no yes

Save reports to Azure Blob storage, Azure Files or Azure Data Lake Storage, by selecting Azure storage account.

Learn more >>

Saving to Azure storage with metadata fields no

no no

Save reports with metadata fields to Azure Blob storage, Azure Files or Azure Data Lake Storage. Metadata fields can be useful for integration scenarios.

Saving to Attachments no partially

Only via e-Invoice attachment and limited to journal records.

yes

  • Select Document and Record type (e.g. Journal, Sales order or Customer) that the printing report should be attached to.
  • Introducing Category, Language, Active From and To, Tags.

Learn more >>

Configurable Azure storage for Attachments no no no

  • You can configure Document types to store Attachments to a particular blob container and blob path on D365FO Azure Blob storage, or to a particular file share and folder path on D365FO Azure Files.
  • Additionally, you can set up the access tier when saving Attachments to Azure Blob storage.
  • On the roadmap to support advanced setup per entity, e.g. which file share and folder path or SharePoint library to use when attaching files to Customer, Sales order, etc.
Configurable external Azure storage for Attachments no no no

You can configure Document types to store Attachments to an external Azure Blob or File storage.

Archiving
Print archive partially

ER Print archive contains all executed ER jobs with no search capabilities. Users can choose different Document type per report and this way save invoices and orders in different locations (e.g. different SharePoint folders).

partially

SSRS Print archive contains only one meaningful field – Report caption, which gets populated either from the report menu item label (e.g. ‘Show invoice’) or the report technical name (e.g. PurchPurchaseOrder.Report). No other metadata such as Document ID or Account name is available.

The same Document type is used for archiving all reports, it cannot be configured and is set to the first Document type having Group ‘File’.

yes

  • Great search capabilities per report metadata, e.g. Customer, Sales ID, Invoice ID.
  • Access from Customer and Vendor cards.
  • View print settings and report parameters of archived reports.
  • Specify a note on the Print destination settings form and use it when searching archived reports.
  • Use different Document type per report and save invoices and orders in different locations.

Learn more >>

Print archive preview no no no

Previewing archived reports from within Print archive, without downloading them previously.

Download single, multiple or merged PDFs no no

Users can download archived report documents one by one.

yes

From Print archive you can download single, multiple or merged PDFs. You can also download the outgoing email messages and the documents generated in the output format different from PDF.

Archive outgoing emails no no no

In addition to archiving email print settings and email attachments, you can opt-in to archive the outgoing email messages. They will be stored as configured through the corresponding archiving Document type, e.g. a specific SharePoint site and folder.

Change Azure access tier for archived reports no no no

The access tier of the archived reports saved to Azure Blob storage via Print archive can be changed to the most affordable tier – Archive. You may find this suitable for reports archived in past years. Learn more >>

Print to network printers no no no

Printing (also in batch) of archived reports to network printers will be supported.

Report Viewer
Printing to Screen partially

  • Supported via Word and Excel Online.
  • For PDF templates, PDF extension for web browser is used.
yes

  • Integrated within D365FO.
  • Download as PDF.
  • Print to local printers.
yes

  • Integrated within D365FO.
  • Download as PDF.
  • Print to local printers.
  • On the roadmap: Download an email message with the report PDF document attached.

Learn about differences between SSRS and Docentric Viewer >>

Print to network printers no yes no

Printing to network printers from Docentric Viewer also supports:

  • User default printer,
  • User favorite printers,
  • User allowed printers,
  • Report restricted printers.
Deep links no yes yes

Deep links are shareable and secured URLs to specific forms in D365FO. Learn more >>

Export to Word and Excel no yes

From SSRS Viewer you can export to Excel (.xlsx) and to Word binary file format (.doc).

However, exported Word documents are usually not well formed, because SSRS reports are designed to produce fixed documents such as PDF and not flow documents such as Word.

partially

From Docentric Viewer you can export to Word (.docx) the reports based on Docentric templates, and export to Excel (.xlsx) and Word (.doc) those reports based on SSRS designs.

On the roadmap to enable ‘Export to Excel’ also for reports based on Docentric templates.

You don’t see what you are looking for?

Contact us
or request a new feature right away.

REQUEST A FEATURE

Any questions?

Contact us to clear up any doubts together
or download Docentric now and get the first-hand experience.

DOWNLOAD NOW