27.4

Changelog for Golden EDI version 27.4 that was released on 2026-02-04

Description

Welcome to our latest release! This is a small but crucial release where we've introduced important improvements to how Golden EDI stores message data, along with enhancements to the communication between Business Central and our Cloud Platform. These changes are designed to ensure long-term reliability and better performance for all customers.

Why we made these changes

Message Line Storage (V2)

Over time, as customers send and receive large volumes of EDI messages, the underlying database table that stores the message contents can accumulate a large number of records. The current table that stores this information had some technical limitations that could cause performance issues and technical limitations when the volume got large.

To address this, we've introduced a new table for this data that removes this entirely. This will ensure that Golden EDI can continue to handle your flows and EDI for years to come, regardless on how many messages you process.

Cloud Platform Integration

We've also updated how the communication works between your Business Central and our Cloud Platform. We've co-located some of the information into one API to reduce the number of calls we need to make to your system. Resulting in improved performance and lower load on our systems.

What this means for you

For Most Users: No Action Required

• All new messages created after the updated will automatically use the improved table.

• Your existing workflows, mappings, and configurations remain unchanged.

• You should not notice any difference in how you use Golden EDI.

For Existing Messages

Messages created before this updated will continue to work as before. If needed, administrators can upgrade individual messages to the new table. This is optional and only necessary in specific support scenarios.

For Partners and Integrations

If you have custom integrations using the Golden EDI API:

• The API contract version has been updated to version 3.0

• New API endpoints (v2.0) are available for the updated message line structure

• The Message Queue API now includes Direction and Connection ID fields directly, reducing the need for additional API calls

• Existing v1.0 API integrations continue to function normally

We recommend reviewing your integrations and updating to the v2.0 API endpoints when convenient to benefit from the improved structure

Changelog

Golden EDI

• Introduce Message Lines V2 table to replace the previous message line storage.

• Added Direction and Connection ID fields to the message queue for improved API usage.

• Updated API contract to version 3.0.

• Added v2.0 API endpoints for messages lines and message queue to utilize the new tables and fields.