Skip to main content

Changelog

You can read the Microsoft help if you want to update this app to the latest version and are not sure how to do this. We have also created this animation to show you how.

Important
  • Do not update apps while users are working, as it can cause a disruption and loss of work.
  • It is always best to install updates in a Sandbox first and test them to ensure no adverse effects.

27.0.21.0 - 2026-08-03​

Fixed​

  • Fixed outbound HTTP event messages translating JSON property names when Business Central was set to a non-English language.

27.0.20.0 - 2026-07-29​

Changed​

  • Improved the reprocess experience for failed integration messages by introducing clearer operator guidance and support for retaining the existing retry chain when reprocessing. Read more
  • The default failed-message handling in Integration Hub Setup now uses Delete Failed Messages After Successful Import to better support cleanup after successful retries.
  • Updated the documentation for time zone handling to clarify Default Time Zone, UTC background-processing context, and where time zone settings are applied. Read more

27.0.19.0 - 2026-07-23​

Added​

  • Added activity cues to the Order Processor Role Center. #98398

Changed​

  • The Find Entries (External) action is now promoted to the Process (home) category on the Sales Order, Posted Sales Invoices list, and Posted Sales Shipments list for quicker access. #98398

27.0.18.0 - 2026-07-16​

Changed​

  • Boolean values in outbound HTTP messages now default to true/false — a new Use Boolean Format in Messages setting has been added to the Integration Hub Setup page. For new installations this defaults to enabled, so boolean fields (e.g. isproduction, base64encoded) are sent as true/false rather than Yes/No. Existing installations retain the previous Yes/No behaviour by default, ensuring no impact on Logic Apps or other integrations that rely on those values.

27.0.17.0 - 2026-07-11​

Fixed​

  • Fixed locale-sensitive boolean formatting in outbound HTTP payloads that caused a 400 Bad Request error when Business Central was set to Polish language. #97221

27.0.16.0 - 2026-07-10​

Fixed​

  • Resolved an issue when generating outbound messages where fields targeting the same element were written into separate elements. They are now merged into the same element again.

27.0.15.0 - 2026-07-04​

Fixed​

  • Export/Import Integration Handlers now includes additional subscribers — the Export Integration Handlers action did not include a handler's additional subscribers (child handlers). Importing the exported file therefore recreated the handler without them, so outbound events produced fewer messages than expected. Additional subscribers are now exported and re-imported together with their parent handler.

Changed​

  • Minor internal changes to enhance the app's automated testing.

27.0.14.0 - 2026-07-03​

Fixed​

  • Outbound XML/JSON export fails for Data Exchange Definitions with short column paths — resolved an error where outbound exports using Data Exchange Definitions with column paths that do not include the Data Line Tag prefix (e.g. /fieldname instead of /root/parent/fieldname) would fail during file generation. This regression was introduced in version 27.0.10.0 as a side-effect of the export line numbering change. Definitions that previously produced flat JSON or XML output are no longer affected.

27.0.13.0 - 2026-07-02​

Fixed​

  • Export crash when snapshot is not active — resolved an error during outbound export when the snapshot manager had not set a record variant for the session. The export now falls back to opening the source table directly, so exports work correctly regardless of whether a snapshot is in use.

27.0.12.0 - '2026-07-01'​

Fixed​

  • Sample Config. packages - Error when downloading sample config. packages has now been resolved.

27.0.11.0 - 2026-06-26​

Fixed​

  • Resolved minor visibility and field state issues on the Outbound Integration Message Handler page.
  • Resolved an issue in the assisted setup wizard.

27.0.10.0 - 2026-06-24​

Added​

  • Outbound Granularity — consolidate multiple records into a single outbound message instead of sending one message per record, reducing file count for batch exports. Read more
  • CSV export — export data as comma-separated files with configurable encoding and delimiters via the Data Exchange framework. Read more
  • Include Column Headings — optionally output a header row in Variable Text and Fixed Text exports so receivers can identify columns without external documentation. Read more
  • XMLport and Codeunit payload generation — generate outbound payloads using your own XMLport or Codeunit, giving full control over output format beyond what Data Exchange Definitions offer. Read more
  • Message Body Viewer — the Message Details page now renders message payloads with automatic format detection, syntax highlighting, and a collapsible tree view for JSON and XML. CSV payloads are displayed as a formatted table with column headers. A raw/formatted toggle and expand/collapse controls are provided. Read more
  • Additional sample configurations — new samples covering CSV and JSON exports, including multiple-record processing examples. Access them through the setup wizard in a Cronus company.

Changed​

  • Unlimited export records — removed the previous cap on the number of records that could be processed per export level, enabling large-volume batch exports without workarounds.
  • Snapshot — sync watermark now advances even when no messages are sent — the Synch. Modified On Filter now advances at the end of every sync run, even if the snapshot suppressed all exports. This prevents unchanged records from being re-evaluated on every cycle. See Sync Watermark Behaviour with Snapshot for details.
  • Export line numbering simplified — multi-level Data Exchange exports now assign sequential line numbers (1, 2, 3…) instead of using gap-based numbering (10000000, 10000, 100…). The old gap-based scheme was the cause of the record-count limitation on exports. The internal GetLevelIncrement function has been removed. These line numbers are only used internally during file generation and are not written to the output payload. If you have a custom subscriber that reads Data Exch. Field line numbers during export processing, see Export Line Numbering for details.
  • Default Mapping Codeunit — new Data Exchange Mappings for Integration Hub definition types now automatically set the Mapping Codeunit. If you previously relied on a custom mapping codeunit, you may need to update the mapping after creating it.
  • Snapshot watermark change notification — when you change the Synch. Modified On Filter on a handler that has active snapshot data, a message now reminds you that snapshot records are not cleared and previously suppressed records will remain suppressed until their tracked fields change.

Fixed​

  • Data Formatting Culture — exports now correctly apply the culture specified on Data Exchange Column Definitions, producing correct decimal separators and date formats.
  • Blank dates export as empty strings — blank Date and DateTime values now export as empty strings instead of default values such as 0001-01-01 or 1753-01-01T00:00:00. If your receiving endpoint expects a specific default date for blank values, you may need to adjust the transformation rule or endpoint logic.

27.0.9.0 - 2026-06-08​

Added​

  • Added "Import Integration Handlers" and "Export Integration Handlers" actions on the "Outbound Integration Handlers" and "Inbound Integration Handlers" pages to import and export of integration handler configurations including the related tables and Data Exchange Definition defined on the handler(s).

27.0.8.0 - 2026-06-08​

Added​

  • Added the Delete Data Exchange Payload setting on inbound and outbound integration handlers. When enabled, Data Exchange payload records are deleted after processing to reduce table growth and storage usage.

Fixed​

  • Resolved an error when exporting EFT files using Custom payload generation on outbound integration messages.

27.0.7.0 - 2026-05-26​

Added​

  • Outbound integration handlers now support custom payload generation, allowing payloads to be provided upfront or generated dynamically via extension subscribers. See Payload Generation Method for details.

27.0.6.0 - 2026-04-29​

Added​

  • The Import XML/JSON File Structure action on the Data Exchange Column Definitions page now supports JSON files in addition to XML. Select a JSON sample file and the app will convert it to XML internally, deduplicate repeated paths caused by arrays, and pre-populate column definitions with one entry per unique field. Only element-type nodes are imported — attributes and namespace declarations are excluded.

  • Added a new Validate JSON Message field to Integration Hub Setup. When enabled, the app validates that incoming JSON content is well-formed before attempting to import it, providing a clear error message immediately if the file is invalid. This setting is enabled by default on new setups.

Changed​

  • The Append Root Node field on the Data Exchange Definition card has been deprecated and will be removed in version 28.0. The JSON import process now automatically attempts conversion with and without a root node wrapper, making this manual setting unnecessary.

Fixed​

  • Resolved an issue when exporting integration message content to a file. The downloaded file now uses the correct extension based on the content type — .json for JSON, .xml for XML, and .txt for all other formats. Previously, the file was always exported with the .xml extension regardless of the content.

  • Resolved an issue where an invalid JSON file would produce a misleading error during XML conversion. The JSON is now validated upfront before any processing, so an invalid file is rejected immediately with a clear error message.

27.0.5.0 - 2026-04-29​

Added​

  • Updated xmlport "ImpExpDataExchDef&Map_IH_TSL" with LineSeparator field

27.0.4.0 -2026-04-28​

Fixed​

  • Reverted the Append Root Node changes introduced in 27.0.2.0 due to downstream issues identified during testing. The JSON import behaviour is restored to its previous state.

27.0.3.0 -2026-04-19​

Added​

  • Added a new integration event OnBeforeEDIVarianceStatusUpdate on the Sales Line table extension. This event fires inside UpdateSalesLineEDIStatus immediately before the EDI Variance field is assigned, giving subscribers the opportunity to override the computed variance flags (PriceVariance, OrderMultipleVariance, PriceOverride) and the converted EDI quantity in base units (EDIQtyInBase). Use this event to apply custom variance detection logic or tolerance rules that differ from the built-in behaviour — for example, suppressing a price variance for specific customers or items, or injecting an additional variance condition not covered by standard setup.

  • Added a new integration event OnBeforeSetSalesLine on the Sales Price Detail page (SalesPriceDetail_IH_TSL). This event fires at the very start of the SetSalesLine procedure, before any price detail lines are calculated or inserted into the buffer. Set IsHandled := true to skip all default calculation logic entirely — for example, to replace the standard price breakdown with a fully custom implementation. When IsHandled is false (the default), the standard logic runs as normal.

27.0.2.0 - 2026-04-17​

Added​

  • Added Append Root Node support for JSON Data Exchange Definitions. Read more

27.0.1.0 - 2026-04-15​

Added​

  • Added Outbound event for Transfer Receipt Header is inserted.

27.0.0.0 - 2026-03-30​

Added​

  • Added support for a new Data Exchange Definition type: Process to Excellent Importer (Staged Data). Integration Hub can now map incoming payloads (JSON, XML, etc.) into a generic staging table and automatically trigger Excellent Importer to process the staged data. This enables reuse of Excellent Importer's mapping, transformation, and posting logic without extending business tables or duplicating configuration. Read more
  • Added two new Data Exchange Definition types: Integration Hub Import and Integration Hub Export. Selecting either type automatically populates the recommended codeunit settings for the chosen File Type, removing the need to look up and enter codeunit numbers manually. Read more (inbound) · Read more (outbound)
  • Added an Assisted Setup wizard for Integration Hub. The wizard lets you download sample integration templates (as a RapidStart configuration package) and sample data files (as a zip file) to help you get started quickly. Two sample template packages are available: one for Integration Hub only, and one for Integration Hub combined with Excellent Importer. The sample data is compatible with the Cronus demonstration company. Read more

Changes​

  • Possible breaking change: The Line Offset field on the data exchange mapping now defaults to 0 (previously 10000). When set to 0, line number auto-increment is no longer applied. This change is necessary to support tables where the primary key is an integer but sequential line offset logic should not be applied. If you have existing mappings that relied on the default of 10000, you must explicitly set the Line Offset field to 10000 on those mappings.

26.0.7.0 - 2026-03-30​

Added​

  • Added OnBeforeCreateIntegrationEntry_HTTP integration event to the Endpoint Handler codeunit.

26.0.6.0 - 2026-03-17​

Added​

  • Added outbound event handler for Warehouse Shipment creation, triggered after warehouse shipment posting (OnAfterPostWhseShipment).

26.0.4.0 - 2025-12-17​

Changed​

  • Enhanced the AfterProcessMessage procedure to provide more detailed error diagnostics when detecting recursive modification conflicts. The error message now includes the conflicting integration handler details to help identify which handler configurations are causing infinite loops.

26.0.3.0 - 2025-09-30​

Fixed​

  • Resolved an issue where record filtering logic in the AfterProcessMessage procedure could fail when applying complex table filters during post-processing operations.

Added​

  • Added OnBeforeAfterProcessMessage and OnAfterAfterProcessMessage integration events to provide extensibility points for custom logic during message post-processing operations.

26.0.2.0 - 2025-09-23​

Fixed​

  • Resolved an error with the record validation logic in the OutboundEventMgt codeunit (CheckForValidRecord).
  • Added integration events for record validation.

26.0.0.0 - 2025-09-19​

Added​

  • #78419: Added a "Snapshot Mode" for outbound messages, allowing users to specify which fields should trigger outbound messages. In this mode, messages are only sent when configured fields change, reducing unnecessary system traffic and message clutter. This helps improve integration relevance and system performance, especially for high-volume records. You can read more about this here.

25.0.8.0 - 2025-08-28​

Added​

  • #78883: Add Custom Parameters to the Customer and Vendor pages. This allows you to hold custom configuration settings to support integrations with partners.
  • #78883: Add Label Type enum to Label Values table and page.

25.0.7.0 - 2025-08-06​

Fixed​

  • Resolved an error with the integration via the Excel importer, where the integration entry was incorrectly marked as failed despite the message being successfully processed.

25.0.5.0 - 2025-08-05​

Added​

  • #77847: Add Custom Parameters to the Integration Hub Setup page. This allows you to hold custom configuration settings to support integrations with partners.

25.0.4.0 - 2025-07-02​

Changed​

  • Opened procedures for external access to support migration from the PTE version.

25.0.2.0 - 2025-06-10​

Changed​

  • Opened procedures for external access. Brought procedure from previous version back in.

25.0.1.0 - 2025-05-12​

Fixed​

  • Resolved an issue related to the offset that would occur in some scenarios.

25.0.0.0 - 2025-03-17​

Changed​

  • The Integration Record Id and Processing Message now get updated when the message is processed using Excel Importer.
  • Minor refactoring to prevent future breaking changes.

24.0.17.0 - 2025-03-11​

Added​

24.0.16.0 - 2025-01-28​

Fixed​

  • Resolved an error that would occur when directly setting the message body (InStream variable not initialised).

24.0.15.0 - 2024-12-18​

Changed​

  • Added an event publisher to allow defaulting Trans. Subst Values if missing
  • Removed check on duplicate Outbound Event Description during an upgrade

24.0.14.0 - 2024-11-21​

Added​

  • Resolved a translation issue.

24.0.13.0 - 2024-11-13​

Added​

  • Event/Response Workflow code is now public to enable workflow extensibility.

Fixed​

  • Implement fix for Direct Call when message body is not directly defined

Changed​

  • Overloads on CreateIntegrationEntry_HTTP reverted from internal to external

24.0.12.0 - 2024-11-08​

Fixed​

  • Implemented a fixed on time zone offset handling. Read more

24.0.11.0 - 2024-10-25​

Changed​

  • API Endpoints and Integration Handlers must now specify a Code.
  • Making direct calls to endpoints without dependency on Azure Integration Services is now possible.
  • Added support for handling responses received from Outbound HTTP calls.
  • Added support for running a custom Codeunit on inbound handlers to perform custom logic relating to inbound messages.

24.0.10.0 - 2024-10-03​

Changed​

  • Functions to set and get the Partner Reference ID and Partner Reference Field ID are now external to support extending the functionality on Inbound and Outbound messages.

24.0.9.0 - 2024-09-26​

Changed​

  • Updated the time zone logic to determine the offset for future dates. Read more

24.0.8.0 - 2024-09-19​

Fixed​

  • Implemented a change to prevent a date from being imported incorrectly from a Json payload when the date is provided in ISO 8601 format with the Time Zone offset. Read more

24.0.6.0 - 2024-08-28​

Added​

  • Added support to handle import/export the date/datetime using different time zone settings. Read more
  • App now supports the import of null values to decimal and date/datetime fields.
  • Added support for processing outbound events using Next Date Formula

24.0.4.0 - 2024-08-02​

Added​

  • Added support for importing text into BLOB fields

Changed​

  • The message type on the integration message is not longer explicitly converted to uppercase.

24.0.3.0 - 2024-07-31​

Added​

  • Changed some helper functions from internal to external to allow access by extensions.

24.0.2.0 - 2024-07-30​

Added​

  • Added a comments field to the data exchange line definitions, column definitions, mapping and field mapping. This allows you to add comments to the data exchange definition to help you understand the configuration.

24.0.1.0 - 2024-07-05​

Changed​

  • The app now supports exporting a Json payload using the data exchange definition (We also added this to the PTE Version - 23.0.9.0).

24.0.0.0 - 2024-07-01​

Changed​

  • The Integration Hub is now available on AppSource. We will continue to support the PTE version of Integration Hub and will shortly provided a migration path for customers to move from PTE to AppSource.

23.0.7.1​

Changed​

  • Import JSON to Data Exchange was updated to use UTF-8 encoding to provide support for special characters like the Macron.
  • You can now export to a JSON using a data exchange definition - it is no longer necessary to convert this as a separate action.

23.0.8.0 - 2024-07-05​

Changed​

  • Convert outbound message from XML to JSon format, when DED is configured with File Type "Json".

23.0.7.0 - 2024-05-02​

Changed​

  • Added a new event OnAfterImportHandlingForLineDefChilds.
  • Add new helper functions to the additional information table.

23.0.6.0 - 2024-04-28​

Changed​

  • Added some additional online help and updated context sensitive help on some pages to additional help information.

23.0.5.0 -2024-04-23​

Changed​

  • In 23.0.0.0 we resolved an issue where the app was removing CR/LF from flat text files. This change affected some integrations that were expecting the CR/LF to be removed. We have now added a setting to the API Endpoint and the Integration Handler to allow you to specify if these characters should be removed.

23.0.3.0 -2024-04-04​

Added​

  • Added a codeunit Export XML Content to enable extraction of data using XMLPort.

23.0.2.0 -2024-04-03​

Changed​

  • It is now possible to turn on/off the using workflows to handle integration events. Most integrations use the integration handlers because they perform better. In these cases, turning off the integration workflows can positively impact performance - even if you are not using them for integration. This is enabled by default for existing integrations. This is turned off by default for new integrations. You can change this setting on the Integration Hub Setup page.

23.0.1.0 -2024-03-22​

Fixed​

  • Resolved issue with the Net Unit Price calculation on credit memos.

23.0.0.0 -2024-03-07​

Fixed​

  • Resolved issue where CR/LF would get removed from flat files.

22.0.12.0 - 2023-12-13​

Fixed​

  • Resolved an issue with the creation of the integration event entry when using the internal grid option. In some scenarios the app would raise an error about an invalid date.

22.0.11.0 - 2023-12-06​

Fixed​

  • Resolved an issue with the queued integration messages where an error would occur because one of the fields being filtered on had changed.

22.0.8.0 -2023-11-15​

Fixed​

  • Resolved an issue where a user needed modify permission on the integration event entry table.

22.0.7.0 -2023-10-26​

Added​

  • Added a new outbound event called Synchronise in the background using ModifiedAt date/time (per record). If you create an outbound handler using this method, you must create and schedule a job queue entry for Codeunit OutIntSyncRunner_IH_TSL. Here are some more details.
  • Added telemetry to record when new integration messages are created and to record outbound API calls.

22.0.6.0 -2023-10-16​

Fixed​

  • Removed an explicit commit that was added for outbound messages in 22.0.5.0.

22.0.5.0 -2023-10-13​

Added​

  • It is now possible to create outbound messages but delay the transmission of them. This allows you to prevent the transmission of messages during a large transaction that subsequently fails and rolls back. The are also possible performance gains as you no longer need to wait for the message to be transmitted. Scenarios where this approach may be useful:
    • When sending advanced shipping notices or invoices that get created by posting warehouse shipments relating to many orders
    • Preventing delete messages from being sent before the record is actually deleted

Changed​

  • Sales Lines of type G/L Account not longer not get checked for EDI price variances.

22.0.1.0 -2023-09-22​

Fixed​

  • Removed Item Cross Reference table extension

22.0.0.0 - 2023-09-08​

Fixed​

  • Resolved an issue on sales line - net unit price update

Added​

  • Added Skip Error on Failed call to Endpoint API
  • API v2 page
  • OAuth2.0 and secret handling implemented
  • API field name fixes
  • Journal Posting Support
  • Group caption
  • Partner Reference Id added, set to text 1024
  • Fix for blank details on HTTP call
  • Final fix - CRLF breaking APIM - replaced with ''

21.2.4.0 - 2023-08-29​

Added​

  • Added the Process Mapping field to the Data Exchange Mapping. This field is an extensible enum, which you can use to indicate special processing.

21.2.3.0 - 2023-06-21​

Fixed​

  • Resolved an issue that would cause certain outbound transactions to fail due to a "XML Buffer does not exist..." error.

Changed​

  • Made a change to the data exchange definition setup to suppress a confirmation message when importing using a data exchange configuration.

21.2.2.0 - 2023-06-07​

Changed​

  • Minor refactoring to the sales price variance workflow.

21.2.1.0 - 2023-05-18​

Fixed​

  • Resolved an error on the sales price variance workflow that impacted rejections and cancellations.

21.2.0.0 - 2023-05-17​

Changed​

  • The sales price change tracking feature was changed to have an option where you only track changes to prices and you do not track changes to discounts.

21.1.5.0 - 2023-04-28​

Added​

  • It is now possible to change the status of the integration event entry when using an error classification.

21.1.3.0 - 2023-03-24​

Changed​

  • Add key with "Barcode Classification_IH_TSL" field in "Item Reference_IH_TSL" table extension.

21.1.2.0 - 2023-03-22​

Changed​

  • The "EDI Message" field on the sales header now gets set to false when you copy an existing document.

21.1.1.0 - 2023-03-14​

Fixed​

  • We changed the validation related to EDI/Sales Price Approvals was refactored to support legitimate changes to a sales document during the shipping process. This issue was only reported when using the over/under shipping feature from the Dual Unit of Measure extension.

20.1.0.0 - 2023-01-24​

Added​

  • We now support importing a JSON File using ImportJSONToDataExch_IH_TSL as a Reading/Writing Codeunit

20.0.16.0 2022-11-28​

Fixed​

  • Resolved an issue where two simultaneous messages could get the same Id assigned when using the line offset.

20.0.15.0 2022-11-28​

Fixed​

  • Change the date filtering on the integration activities part for the current date so that it works correctly for on-prem and cloud environments.

20.0.14.0 2022-11-28​

Added​

20.0.13.0 2022-11-28​

Added​

  • It is now possible to classify failed integration messages based on rules. The classification assists with faster resolution of failed integration messages - especially during UAT when handling complex integrations with high transaction volumes. You can read about how to use this here.

20.0.12.0 2022-11-24​

Changed​

  • Integration Handler properties are no longer case-sensitive
  • Update the latest error message onto the original integration message when reprocessing messages. This is helpful because sometimes the integration fails due to record locking and then when you try again it has a different error.

20.0.10.0 2022-11-24​

Added​

  • You can reprocess multiple failed messages from the Integration Messages page by selecting the Reprocess Messages action. Reprocessing messages can cause duplication so skilled consultants should only use this.
  • A new Cancel Message action is now available on the Integration Messages page, which allows you to cancel integration messages that failed and have been handled manually.
  • The Notes and Links parts are now available on the Integration Messages page, which allows you to enter details about the message, for example, if you cancel the message.

20.0.8.0 2022-11-21​

Added​

  • Added Event Topic and Subject to the API Endpoint table. These fields get used as defaults when setup up new integration handlers.
  • Handle Json Escape characters on all messages generated from the Integration Hub.
  • Fix issue with Effective Permission blob
  • Added Field Type filter to avoid getting stuck on table filter.
  • Added a new outbound event that can be triggered by a custom extension to export any record.

[20.0.6.0] (2022-09)​

Added​

  • Added "Save Template" and "Apply Template" action to the data exchange definition card and data exchange mapping card pages. This allows you to more easily save and reuse the template.

[20.0.2.0] (2022-08-01)​

Added​

  • Added a new outbound integration handler event OnAfterProcessInboundIntegrationMessage - An inbound integration message processed. Use this event to immediately export a record after it is imported from an inbound integration message. An example of where this may be useful is when you want to provide an order confirmation message.
  • Implemented subscription subscription management to versions 15 and greater

[19.2.5.0] (2022-07)​

Changed​

  • When sending to Endpoint, Business Center will error out if http response code is not within 200 to 299.

[19.2.4.0] (2022-06)​

Added​

  • Added an order address outbound event

[19.2.3.0] (2022-06)​

Fixed​

  • Fixed an issue on the Outbound Integrations Handlers were it displayed an error that that Integration Handler did not exist.

Added​

  • Added a "Copy from" action to the integration handler list and card pages. This allows you to more easily duplicate the handler when this is a requirement.

[19.2.1.0] (2022-05)​

Added​

[19.2.0.0] (2022-04)​

Added​

  • Additional Subscribers on Outbound Messages allows you to send the same record to more than one endpoint.
  • Added the *Integration Record ID- to integration messages. The purpose of this field is to provide a link between the integration message and the source/destination of the integration message.

Changed​

[19.1.5.2] (2022-01)​

Added​

  • Added a Find Text action to the Integration Messages Page

[19.1.4.0] (2021-10)​

Fixed​

  • Resolved an issue with the integration handlers where RunWorkflowOnForPostedSalesCreditMemoOnAfterPostSalesDoc(SalesCrMemoHdrNo: Code[20]) was raising the invoice event.

[19.1.3.0] (2021-10)​

Added​

  • Added an Integration Activities page that can show you the status of integration messages.

[19.1.2.0] (2021-09)​

Removed​

  • Removed the page extension for Item Cross Reference entries. This is no longer available and is a breaking change for V20.

[18.0.28.0] (2021-08)​

Fixed​

  • Resolved an issue with the Approval of EDI variances.

[18.0.12.0] (2021-07)​

Added​

  • Added cost and margin to the sales price detail. By default this is not shown. Enable this on Integration Hub setup.

[18.0.10.0] (2021-07)​

Added​