Bug Fixes

Credit – Mixed VAT Bug

An issue with credits has been resolved that affected documents with mixed VAT lines. The amount shown in the transaction log differed from the amount actually transmitted to collana pay. Only credits with lines containing different VAT rates were affected (e.g. 19% and 0% VAT simultaneously).

Improvements & Enhancements

Simulation – No Cart and Recurring Payments

Simulation support has been extended to cover Recurring Payments and No Cart transactions. Both transaction types can now be tested in the simulation environment.

Publisher – SplitAddress Error

A new publisher event is now available in the PAYWebServCommunication codeunit that fires when the SplitAddress function is unable to parse an address.

• The OnBeforeSplitAddressError event is triggered in both the AddBillingCustomerData and AddShippingCustomerData methods.
• The IsBillingAddress parameter indicates the context in which the error occurred (true = billing address).
• Subscribers can set Street, HouseNo, and IsHandled := true to provide their own address data and suppress the error.

Handling of "Unsupported" Responses

The handling of collana pay responses with the status Unsupported has been changed. Previously, these responses were treated the same way as successful notifications, which caused issues with some payment providers that automatically extend reservations.

Unsupported responses – mostly void interactions – are now handled as failed interactions and must be reviewed manually. A new cue for failed reversal entries has been added to the collana pay Role Center for this purpose.

Modifying Transaction References

Editing Reference 1 and Reference 2 on transactions as well as on sales orders and sales invoices is now restricted to defined conditions.

• Changing the reference fields on the sales header or on the transaction automatically triggers an update of the respective other record.
• The page update trigger has been removed as it is no longer required.