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
On Azure or SharePoint yes

Attachments (Azure/SharePoint)

no

AOT

yes

AOT/Azure/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 TFS.

yes

Supported via SharePoint/TFS.

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 >>

Adding new label translations by end-users yes no yes

Document generation
Embedded in D365FO partially

Depends on Microsoft Office 365 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 365 cloud service.

yes yes
Word output format partially

Supported for documents designed in Word.

no 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.

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

Implemented with barcode fonts.

partially

Implemented with barcode fonts.

yes

Embedding subdocuments / attachments partially no yes

Merging documents / attachments by end-users no no no

Merging documents / attachments by developers no no yes

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 >>

PDF Signature no no no

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

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

PDF/A and PDF Attachments no no no

General
Integration with other SSRS reports no yes yes

Any SSRS report can be used with Docentric but also can be converted to Docentric CBD report, which means that end-users can add additional data to reports and print them to improved Docentric print destinations.

Learn how to convert SSRS Check to CBD >>

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 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.

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

Print management
Integration with Print management partially

  • 'Preview copy/original' does not work (works with SSRS).
  • 'Use print management' works but the print destination selected in Print management is ignored. Instead, the configured ER destinations are always used.
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 >>

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 >>

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 local 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. Administrator can set up default printers for all users.

Learn more >>

User-Favorite printers no no no

End-users can select their favorite printers, which will appear on the top of the list of all available network printers when printing reports. Administrator can set up favorite printers for all users.

Report-Restricted printers no no no

Administrator can restrict the selection and use of particular network printers per report. Users can print a report only to network printers allowed for this report.

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 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.
Load from Email templates no no no

Email body can be pre-loaded by selecting a particular Email template and modified further if needed.

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 no

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.

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 >>

Sending emails via Email distributor batch no no yes

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

Learn more >>

Bcc, Reply-to, Bounce-to and Message priority no no yes

Read and Delivery receipts no no yes

Printing redirection from Email to Printer if the account email is missing no no yes

Order Email and Project Email email tokens no no yes

Additional email attachments by end-users no no yes

Additional email attachments by developers no no yes

e-Invoice attachment no yes yes

Advanced reporting scenarios no no yes

Email templates for workflow and retail notifications no no yes

Saving to SharePoint, Azure and Attachments
Saving to SharePoint yes

Supported via Print archive and Power BI.

no yes

Saving to SharePoint with metadata fields no no no

Saving to OneDrive no no yes

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 external Azure storage no no yes

Save reports to an Azure Blob storage or Azure Files, by selecting Azure storage account.

Learn more >>

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. User can only choose different Document types per report and this way save invoices and orders in different locations (e.g. different SharePoint folders).

partially 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 >>

Download single, multiple or merged PDFs no no 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.

Changing 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.

Learn about differences between SSRS and Docentric Viewer >>

Deep links no no yes
Export to Word and Excel no no yes

From Docentric Viewer you can export to Word reports based on Docentric templates, and export to Excel and Word 2003 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 FEATURE

Any questions?

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

DOWNLOAD NOW