Breeze Interface for Dynamics 365 BC - en-US
Manual for the administration and use of BREEZE for Microsoft Dynamics 365 Business Central. We deliver our all-in-one BREEZE workflow solutions for document-oriented business processes from a single source, whether as OnPremises or as Solution-as-a-Service. The BREEZE workflow engine quickly steers documents and data through the entire review process with simple "if-then" rules and conditions, all the way to final approval.
- System Requirements
- Installation
- Configuration & Administration
- Permission sets
- DEXPRO Core
- Breeze Interface Setup
- Document Class Setup
- Target Template Setup
- Generic Custom Fields
- OAuth 2.0 setup (for SaaS only)
- Breeze Workflow
- Application / Usage
System Requirements
System requirements for using BREEZE for Dynamics 365 BC
Supported Microsoft Dynamics 365 Business Central versions
Microsoft Dynamics 365 Business Central integration is possible from the following version due to minimum technical requirements:
Supportet Microsoft Dynamics 365 Business Central Versions
The prerequisite for operation is that the respective Microsoft Dynamics 365 Business Central version is still in regular support. The extended support is excluded.
Supported BREEZE versions
A licensed BREEZE system is required to connect BREEZE to Microsoft Dynamics 365 Business Central and for operation.
- minimum Documents Version: Documents 5h #2311
- minimum DEXPRO Invoice Solution Version: Invoice 1.1.015
Installation
Licenses
Microsoft
Information about the Microsoft Business Central licenses.
BREEZE
The DEXPRO BREEZE system that should be connected to Business Central requires a valid customer license.
Obtaining the DEXPRO modules
Detailed informationen are here.
OnPrem
For OnPrem installations, an runtime package with the required apps is provided upon request of a registered reseller / partner. These modules are added to the customer license by the partner and then imported into Microsoft Dynamics Business Central. It should be noted that the DEXPRO Core module forms the basis for all DEXPRO modules and must therefore be imported first.
Cloud
For cloud installations, you only need the Microsoft AppSource. This is where the required DEXPRO modules are downloaded.
Configuration & Administration
Permission sets
In order to use the modules, the appropriate authorization set must be assigned to the respective users.
The following are supplied with:
-
DXP Core Admin - DEXPRO Core Administrator
-
DXP Core User - DEXPRO Core User
- DXP BREEZE Admin - DEXPRO BREEZE Administrator
- DXP BREEZE User - DEXPRO BREEZE User
DEXPRO Core
The DEXPRO Core manages the individual DEXPRO apps and their documents per client.
All documents that have been entered and processed via the various DEXPRO modules in Microsoft Dynamics 365 Business Central are displayed. A global number series, which is used across all DEXPRO apps, is used to complete individual documents. This offers the advantage that users only have to work with one number series per document.
Further information can be found here.
Breeze Interface Setup
In the Breeze Interface setup, processing is set up within the app.
Process
Copy Setup
This copies the setup to other clients.
Navigation
Document class setup
Target Template Setup
General
In this FastTab you can enable/disable the use of this app.
No. Series
The number series for the Breeze Interface documents is stored here.
Document Class Setup
In the document class setup, the mapping between the respective document class and your export interface is done. Furthermore, the field mapping of each document class is downloaded here, creating a set of standard fields and their usage in Microsoft Dynamics 365 Business Central.
The document class setup is cross-app and is managed via the DEXPRO Core.
Process
Download field mapping
This downloads the field structure of the SQUEEZE document class. These are needed for the metadata mapping.
Navigation
Metadata mapping
List
Document classes
This overview lists all the document classes that have been set up.
Card
Document class
Here, each document class is set up individually.
General
In this fastab the name of the document class, the next process step, as well as the automatic enrichment of the positions is set up.
Breeze
Here you can set the default target template for this document class.
The following are available as standard:
Target Template Setup
Target templates for the Breeze interface are managed here. These templates are available by default:
General
Here you can see which target template is currently being edited.
Plausibility Check
Here, certain plausibility checks per target template can be deactivated.
Generic Custom Fields
OAuth 2.0 setup (for SaaS only)
Access to web services in Microsoft Dynamics 365 Business Central (BC) in the SaaS version is only possible via OAuth 2.0. The necessary setup of the app in Azure Active Directory and its link to BC is described below.
Azure Portal
Launch Azure Portal and open the Azure Active Directory
Create a new app under App registrations
Create API permissions
The Application (client) ID can already be copied and stored at this point (will be needed later)
Create Client secret and store it in a secure location
Business Central
Open Azure Active Directory applications and create a new entry
Set up Active Directory application
- Enter the Client ID
- Enter description (description is a bit misleading. This is rather a user name).
- Assign user permission set(s) individually.
- (Optional)
- Activate application
Breeze Workflow
To connect our Breeze Invoice Workflow to Dynamics 365 BC please read this manual.
Application / Usage
This describes the process from the provision of validated squeeze purchasing documents to external workflows to the posting transfer of released documents.
Breeze Interface Documents
All documents that are in the Breeze process are listed here.
Statuswerte
- WaitingForRetrieval: The document is ready and waiting to be picked up by the workflow system.
- Retrieved: The document was picked up by the workflow.
- Processed: The document was processed successfully.
- Error: The document has at least one error, which must be corrected in the workflow.
- Rejected: The document was marked as rejected by the workflow system.
- WaitingForJson: The document is waiting for the Json file to be enriched.
- ChangeCompany: The document is waiting to be processed by the background process and transferred to another client.
Transfer to the unposted purchasing documents
After the workflow system has released the purchasing document, it is transferred to the Breeze interface. A plausibility check is then performed in the interface. If the check is successful, an unposted purchasing document is created.
If the plausibility check failed, the document is set to the status "error" and the error message is appended to the respective position in the Json structure of the document. Now the document is again waiting to be picked up and corrected by the workflow.
The unposted purchase document is created with all data from the Json structure. If attachments from the process have been attached, these will also be transferred to the unposted document.
Breeze Interface API
Here you will find the documentation for the following products: