Version: 28.2.0
Release Date: 3 November 2026
Product: Business Central Integration
Release Type: New Features & Enhancements, Bug Fixes
Overview
This release introduces improvements to purchase order item mapping, user interface updates, and localization support for Finland. It also resolves issues related to duplicate invoice creation during invoice synchronization and improves the overall user experience of the Rydoo AP and Business Central integration.
New Features & Enhancements
Improved Supplier Item Number Mapping
Work item: #48517
The purchase order integration has been enhanced to improve item number mapping for Business Central purchase orders. When a vendor item number is not available, the item number is now used consistently for both customer and supplier item references. When both values exist, each field is mapped correctly according to its intended purpose.
Removed "Create Lost Invoices" Action
Work item: #48858
The Create Lost Invoices action has been removed from the invoice list. The action is no longer required with the current connector architecture and its removal helps prevent unintended retrieval of historical invoices while simplifying the user experience.
Updated Invoice Retrieval Action Name
Work item: #49352
The action previously labeled Get Approved Invoices has been renamed to Get Invoices in Posting. The new name more accurately reflects the invoices retrieved by the integration process and provides greater clarity for users.
Resolved Issues
Duplicate Purchase Invoices Created When Attachments Exist
Work item: #48871
Resolved an issue where invoices containing email (.msg) attachments could create duplicate records in the Business Central purchase invoice list each time invoices were synchronized. The integration now prevents duplicate purchase invoice creation during invoice retrieval.
Finnish Reference Number Mapping
Work item: #49274
Fixed an issue affecting the Finnish localization of Business Central where invoice reference numbers were mapped to an incorrect field. Reference numbers are now mapped to the correct Finnish localization fields, ensuring compatibility with Finnish payment processing requirements and validation rules.
Comments
0 comments
Article is closed for comments.