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

System requirements for using BREEZE for Dynamics 365 BC

System Requirements

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.

 

System Requirements

Supported BREEZE versions

A licensed BREEZE system is required to connect BREEZE to Microsoft Dynamics 365 Business Central and for operation.

Installation

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.

Installation

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.

BreezeInterface_icon_appsource.png

Configuration & Administration

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:

Configuration & Administration

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.

Configuration & Administration

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

Via this menu item you reach the setup for the document classes.

Target Template Setup

This menu item is used to access the target templates setup. Target templates for the Breeze interface are managed here.

General

In this FastTab you can enable/disable the use of this app.

image-1694762018332.png

No. Series

The number series for the Breeze Interface documents is stored here.

image-1694762079375.png

Configuration & Administration

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

image-1647269521455.png

Download field mapping

This downloads the field structure of the SQUEEZE document class. These are needed for the metadata mapping.

Navigation

image-1647269553966.png

Metadata mapping

Via this menu item you reach the metadata mapping. This defines which fields are to be transferred to Microsoft Dynamics 365 Business Central and how.

List

Document classes

This overview lists all the document classes that have been set up.

image-1647269475167.png

Card

Document class

Here, each document class is set up individually.

General

image-1694690581281.png

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

image-1694762582536.png

Here you can set the default target template for this document class.

The following are available as standard:

image-1694762618847.png

Configuration & Administration

Target Template Setup

Target templates for the Breeze interface are managed here. These templates are available by default:

image-1694762827872.png

image-1694762866287.png

General

Here you can see which target template is currently being edited.

Plausibility Check

Here, certain plausibility checks per target template can be deactivated.

Configuration & Administration

Generic Custom Fields

Customer-specific fields can be added here that extend or deviate from our standard template. This mapping ensures that this additional content is assigned to the right places.

image-1707821087292.png

The corresponding BC field is assigned to each technical JSON field name.

On the Breeze side, the fields must be added via the additionalFields.

Configuration & Administration

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 Microsoft Entra ID

image-1666695107040.png

Create a new app under App registrations

image-1666695222272.png

image-1666695353025.png

Create API permissions

The Application (client) ID can already be copied and stored at this point (will be needed later)

image-1666698096645.png

image-1666696539153.png

image-1666696558451.png

image-1666696591385.png

Create Client secret and store it in a secure location

image-1666697533453.png

image-1666697558892.png

Business Central

Open Microsoft Entra Applications and create a new entry

image-1747214121234.png

image-1747214145583.png

Set up Microsoft Entra Application

  1. Enter the Client ID
  2. Enter description (description is a bit misleading. This is rather a user name).
  3. Assign user permission set(s) individually.
  4. (Optional)
  5. Activate application

image-1747214264623.png

 

 

 

 

 

 

 

 

 

 

 

 

 

Configuration & Administration

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.

Application / Usage

Breeze Interface Documents

All documents that are in the Breeze process are listed here.

image-1694763197320.png

Statuswerte
Application / Usage

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.

image-1694763696103.png

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.

image-1694763737921.png

Application / Usage

Breeze Interface API

Here you will find the documentation for the following products: