MSR Combi Fixed Features 2026-05

INDEX

• 105588 | Vendor address is no longer synchronized twice
• 108317 | External ID was copied when creating or duplicating a placement detail or rate
• 108418 | Correct error message when creating an invoice in MSF fails
• 109317 | Changing Parent Account and Default Price Agreement at the same time
• 110523 | Price agreement lines with an expense work type could not be synchronized with the OData sync

CONTENTS

105588 | Vendor address is no longer synchronized twice

We fixed an issue where the invoice address of the Account Vendor was unnecessarily synchronized between Salesforce and Business Central. This address is already managed by Business Central (MSF) from the contact, and the redundant synchronization could write the address to the wrong field.

What has changed:

• The option to synchronize the vendor's invoice address fields has been disabled in Interface Management.
• This prevents duplicate or incorrect address changes and improves the stability of the synchronization, especially for OData customers (in particular customers on OData v2).

108317 | External ID was copied when creating or duplicating a placement detail or rate

When creating a new placement detail via 'Create Placement Detail', or when duplicating a placement via 'Clone Placement', the External ID field was copied from the original placement detail. Because the value in this field must be unique, this could lead to an error message during creation. From now on, the External ID field is left empty when a placement detail or rate is created or duplicated.

108418 | Correct error message when creating an invoice in MSF fails

When creating an invoice in Business Central (MSF) failed, a success message was in some cases incorrectly shown in Salesforce. This has been changed, so a correct error message is now displayed when the invoice was not created successfully. This makes it immediately clear when an action needs to be performed again or where there is a problem in the synchronization.

109317 | Changing Parent Account and Default Price Agreement at the same time

When you changed the Parent Account and the Default Price Agreement on an Account at the same time, saving could fail with an unexpected error. This could happen, for example, when both fields were updated together by automation. You can now save both fields in one go.

In addition, changing only the Parent Account now re-checks the Default Price Agreement against the Account hierarchy. Previously that check ran only when the Default Price Agreement itself changed. An invalid combination may therefore show a validation error instead of being saved unnoticed. Only Price Agreements belonging to the Account itself or to a parent Account in the hierarchy are allowed.

110523 | Price agreement lines with an expense work type could not be synchronized with the OData sync

Do you use the OData sync between MSR and Business Central? When a price agreement line had a work type with the hour type Expenses, Declaration or Periodic Payment, the sync failed with the error that the hour type cannot be Expense, Declaration or Periodic Payment, and the price agreement was not saved in Business Central. From now on, these price agreement lines are synchronized without an error message and the price agreement is saved correctly in Business Central.

Overview of this release

🔗 Please find all features from this release here.