Example: integration with Business Central
End-to-end example for using BE-Code in Business Central: setup and tracking in the BE-Code register.
Purpose
This example shows how BE-Code plugs into Business Central and how you can follow the execution through the BE-Code register. The example follows the shipped demo scenario for item identifiers.
Context
- BE-Code runs as a middleware service. Setup is described in BE-Code setup.
- When an item identifier is created or modified, the shipped event subscriber automatically inserts an entry in the BE-Code register and calls the service.
Prerequisites
- The BE-Code service is available (on-premises or Azure Container Instance).
- Basic authentication credentials for the service are at hand.
- The BE-Code app is installed in Business Central.
Process catalog
Process Step 1 – Maintain the BE-Code setup Enter the server URL and authentication, then test the connection.
- In Business Central, open the BE-Code Setup page.
- Enter the server API URL, for example
https://<fqdn>:1880/becode. - Enter the basic authentication credentials.
- If needed, enable the item identifier integration and maintain the API path and the default identifier parameter.
- Choose the Check connection action. A success message confirms that BE-Code is reachable.
Process Step 2 – Verify execution in the BE-Code register Trace the generated entries and stored images.
- Create an item identifier or modify an existing entry.
- Open the BE-Code Register page. One record is created per operation.
- Review the status and the generated images.
The base64-encoded image is stored as a media set. You can reuse the matching GUID identifier in other tables without asking for the image again.
Outcome
- The BE-Code setup is maintained and the connection is verified.
- Every change to an item identifier is processed automatically.
- Generated barcodes are available as a media set in Business Central for reuse.
Links