InterformNG2 - Microsoft Dynamics 365FO Package - Overview
Introduction
Microsoft Dynamics 365 for Finance and Operations (Dynamics 365FO) is an enterprise resource planning (ERP) system from Microsoft, designed for large and medium-sized organizations to manage core business processes such as:
- Finance Management
General ledger, budgeting, accounts payable/receivable, fixed assets - Supply Chain Management
Inventory, procurement, warehousing, transportation, production control - Manufacturing
Discrete, process, and lean manufacturing - Project Management and Accounting
Cost tracking, time management, billing - Retail and Commerce
POS, pricing, customer loyalty, e-commerce - Human Resources (now often moved to Dynamics 365 HR or merged into other apps)
The InterForm Dynamics365FO package is a comprehensive plug & play solution for creation of business documents like, Invoices, Purchase orders, account statements etc.. The package comes with a standard design, which can be modified for corporate branding. Printing, e-mailing, archiving in Sharepoint is part of the standard delivery – ready to go when the configuration is done.
The solution can run on the cloud and on-premise, whatever suits your needs.
A deployment package must be installed in Dynamics365FO. This package makes the integration to the InterFormNG2 server and as reports are added and activated in the package, the reports will be auto converted into xml, passed to the InterFormNG2 server. Printing, e-mailing, archiving is executed as requested by the Dynamics365FO user.
The deployment package also offers an option to enrich standard reports with additional data, making it easier to maintain an ERP solution with less modifications.
The deployment package does not add any new buttons, or way of working, so for the Dynamics365FO user it’s work as usual.
Functionality and contents
We deliver the setup of a standard package where we apply preconfigured content to a test and a production environment.
The standard package consists of, among other things, the following:
- Installation of InterFormNG2
- Installation of the D365 Connector
- Configurable D365 Reports
- InterFormNG2 workflows (printing, mailing, archiving)
- InterFormNG2 resources
- InterFormNG2 D365 document templates (depending on the document package purchased),
- Sharepoint integration module for InterFormNG2
Templates
Customer Account Statement
Template: CustAccountStatement.ift
Proforma Invoice
Template: FreeTextInvoice.ift
Picking List
Template: WMSPickingList.ift
Purchase Order
Template: PurchaseOrder.ift
Purchase Invoice
Template: Purchinvoice.ift
Product Receipt
Template: PurchPackingslip.ift
Interest Note
Template: InterestNote.ift
Collection Letter (1)
Template: CollectionLetter.ift
Collection Letter (2)
Template: CollectionLetter2.ift
Sales Invoice
Template: SalesInvoice.ift
Packing Slip
Template: SalesPackingSlip.ift
Quotation
Template: SalesQuote.ift
Transforms
The Transformation below is used to identify the document number, customer number and template Id from the xml if the data is available otherwise the data is hardcoded in the xml structure specific for the template id. This transformation is made inside of InteformNG2 as an ixt file which can be used to enrich the xml with new data. The main purpose of this transformation is to introduce other nodes to the xml which we will be using in the Dynamics365FO package.
Example
Workflows
We have made 4 pre-configured workflows for the Dynamics 365FO package, which consist of
- listResources
is used by the integration package to get the templates names configured in InterformNG2. This workflow must not be deleted. - reportOutput
is used by the integration package to receive data from Dynamics 365FO. This workflow should not be deleted. - D365FO_ERROR
is made to capture any irregularities within the D365FO_GENERIC workflow which forces the workflow to suspend and then creates a new file in the others folder within InterFormNG2, so the user has access to the xml file which made the D365FO_GENERIC to suspend. - D365FO_GENERIC
This is our main workflow where the input file is being processed, and it is then either previewed, printed, archived, or sent as an email. - D365FO_INBOX_RESOURCES
is input workflows which receives the data as a xml, the latter is made for testing purposes where the user can take the xml file and put it into InterFormNG2 folder in others folder and the workflow will then process the file.
Sharepoint
In InterFormNG2, we have a SharePoint component used to archive PDF documents on the SharePoint site.
In the picture below you can see the standard configuration for the Dynamics365FO package.
We have an office365 instance which is our main connection to the SharePoint site from InterFormNG2. The site which we are using in the SharePoint is D365FO, this can be changed if desired otherwise this site must be created to archive to SharePoint.
The Document library name is document which is standard, and the Output filename is pre-configured to take the node from ReportID and docNO variable which is defined in the workflow as a variable and the transformation file for creating the PDF. Users can change that as desired.
The folder used in SharePoint is listed in the folder section. The user does not need to create the folder in SharePoint; it is done automatically when SharePoint receives the output file for archiving.
We have pre-configured Column names which are DocNumber, DocName and Recipient, these are required to be created by the user otherwise the information will not be filled in these columns. Users can change the column content according to their specifications on SharePoint site. Make sure to update the SharePoint component according to the columns created in SharePoint.
To Sharepoint document library component configuration
PDF/UA-1 complaint
The Dynamics package is prepared with PDF/UA-1 compliant templates. See example below.
Example
As you can see in the picture above, we have prepared some TextStyles for the document which are used for the headers in the documents. These are required for the PDF document to be compliant with the PDF UA standard.
If the PDF documents need to be sent or archived as PDF UA document, then in any component which is ‘’create PDF’’ needs the changes in ‘’PDF target Format’’ to PDF/UA-1 in the workflow. If this is not changed, then the PDF will be rendered as a PDF/A.
Related Articles
InterformNG2 - Microsoft Dynamics 365FO Package - Implementation Guide
General Prerequisites MS Dynamics 365 FO InterFormNG2 Version 4.0.2 InterFormNG2 D365 Solution Package (Export) Dynamics Integration Package (Connector) Connector License D365 Connector Setup Installing the Connector InterForm Report Override ...Solution Documentation - Interform Infor M3 Package
Introduction The InterformNG2 - Infor M3 package is a standardized solution that enables Infor M3 customers to manage and streamline their document output through the InterformNG2 platform. It delivers preconfigured content, document templates, and ...Solution Documentation - Interform Automotive Solution
Interform Automotive Package Interform Automotive Solution is an output management solution developed specifically for the automotive industry. It extends the core functionality of InterformNG2 with a comprehensive collection of industry-compliant ...Integration between SAP S/4 HANA and InterFormNG2
Foreword / Background This documentation outlines the process and requirements for integrating SAP S/4 HANA with InterFormNG2, a solution for managing digital forms and output. It is essential to note that there are multiple approaches and methods ...