Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

MSR Combi Fixed Features 2026-04

Features in the Combi integration where issues have been fixed.

INDEX

  • 100885 | Anonymized candidates not deleted from MSF
  • 103698 | User interface improvements for Calculated Work Types
  • 103885 | End date of previous wage/rate line in Combi was not removed
  • 104595 | Email from follow-up flow was sent twice
  • 104915 | Wage data was cleared while completing the placement wizard
  • 105552 | Improvement: more accurate salary and rate data for proforma calculation (OData)
  • 106436 | CAO description synchronization failed for overly long text from Business Central

Version 2.9.2

  • 107569 | Candidate Not Pre-filled When Opening a Second Salary Data Screen in Console Navigation

Version 2.9.4

  • 109392 | BatchRequest limit during Placement sync

Version 2.9.5

  • 109566 | Bed Planning did not work with a full OData connection

Version 2.9.7

  • 109651 | Changing Employment Contract Status fails when closing the previous contract
  • 109712 | Error when syncing a Car Allocation from a flow
  • 109979 | CAO, wage table, scale and step were not always updated correctly when syncing to MSF
  • 110088 | Sync of payment data to MSF now only for a clear-cut record

Version 2.9.8

  • 110215 | Manual wage was sent along with a wage classification on the employment contract

Version 2.9.9

  • 110298 | Sync of payment data to MSF now only for a clear-cut record

Version 2.9.11

  • 111743 | Unclear error message when an IBAN could not be synced

CONTENTS

100885 | Anonymized candidates not deleted from MSF

When deleting anonymized candidates in MSR, the related data in MSF was not deleted along with them. When the DeleteAnonymizedPersonsBATCH batch ran, candidates were removed from MSR, but their related data remained in MSF. From now on, running this batch also removes the anonymized data from MSF, where applicable.

103698 | User interface improvements for Calculated Work Types

When managing calculated work types on the project resource, various actions and messages were not optimal. The following improvements have been made in this release:

  • Actions directly accessible: Important actions for excluding or overriding work types are now available directly at the top level of the page.
  • Clearer messages: When excluding centrally managed work types (such as those from a collective agreement or price arrangement), a more specific error message is now displayed.
  • Insight into origin: The new field 'Work Type Level' makes it immediately visible from which entity (e.g. Customer or Project) a work type originates.
  • Filter options: Toggle buttons have been added to quickly switch between 'Default Work Types' and 'All Work Types', providing a better overview and faster page performance.

103885 | End date of previous wage/rate line in Combi was not removed

Do you use Wage & Rate synchronization via OData (without full OData synchronization)? When deleting a placement detail from a placement with multiple placement details, the related wage/rate line in Combi was correctly deleted, but the end date of the previous wage/rate line incorrectly remained. From now on, the end date of the previous line is automatically removed correctly, so it matches the current situation again.

104595 | Email from follow-up flow was sent twice

If a wizard was completed from the End Employment action and this started a configured follow-up flow, an email from that flow could be sent twice. This only happened when the follow-up flow contained an email action. From now on, the follow-up flow runs only once when the wizard is completed, so the email is also sent only once.

104915 | Wage data was cleared while completing the placement wizard

We fixed an issue in the Wage step of the placement wizard (Combi). If you hadn't filled in a required field and clicked Next, a validation message correctly appeared. At the same time, however, the wage data you had already entered (such as wage determination, wage scale, and wage step) was unintentionally cleared, so you had to enter it again. From now on, your entered wage data is retained when a validation message appears. You only need to complete the missing field and continue, without having to re-enter everything.

105552 | Improvement: more accurate salary and rate data for proforma calculation (OData)

When calculating a proforma (via the OData connection with Business Central), the salary and rate data is now selected more accurately, so the data in Salesforce and Business Central line up correctly again.

Specifically, this means:

  • Salary data: for each wage component, the most relevant line is now automatically selected. The order applied is: first the level (contract level takes priority over person level), then the business unit (matched to the placement's Cost Business Unit), and finally the most recent valid start date. Only one line per wage component is now sent through.
  • Expense/rate types: only one active rate per work type is now included. A rate without a Cost Centre takes priority; in case of a tie, the rate with the most recent valid start date wins.
  • The Cost Business Unit field on the placement is now required for the proforma calculation. If it's missing, a clear message appears beforehand.

As a result, calculated values such as net wage, cost price, margin, and hourly rate advice are reliable again, and duplicate or irrelevant lines are no longer sent to Business Central.

106436 | CAO description synchronization failed for overly long text from Business Central

When synchronizing CAO descriptions from Business Central to MSR, an error could occur if the text was too long for the field in Salesforce. As a result, the CAO description wasn't updated. This issue has been fixed, so long texts are now processed correctly without an error message.

As a temporary workaround, you can reduce the length of the relevant CAO texts in Business Central so the synchronized content stays within the limit.

Version 2.9.2

107569 | Candidate Not Pre-filled When Opening a Second Salary Data Screen in Console Navigation

When creating a Salary Data record in Console navigation, the Candidate field was correctly pre-filled the first time it was opened from a Contact or Employment Contract. However, if a second "New Salary Data" screen was opened while the first one was still open, the Candidate field remained empty and the context was not loaded.

This has been fixed: the Candidate field (and related context, such as Business Unit) is now also correctly pre-filled when a second or subsequent Salary Data screen is opened.

Version 2.9.4

109392 | BatchRequest limit during Placement sync

A fix has been implemented for an issue where the synchronization of placements (Placement mixed sync) got stuck on an error about too many requests within a BatchRequest. By optimizing and better distributing the processing of these synchronization requests, the maximum number of requests per batch is no longer exceeded. As a result, placements and their related data are synchronized between MSR and MSF again, reliably and without interruptions.

Version 2.9.5

109566 | Bed Planning did not work with a full OData connection

If the connection with MSF ran entirely via OData, Bed Planning did not work. This was solved.

Version 2.9.7

109651 | Changing Employment Contract Status fails when closing the previous contract

When changing the status of an Employment Contract to a sync status, a check is done for overlapping, previously synced contracts. If such a contract is present and you choose to close the previous contract, a sync to MSF is performed. The Id of the previous contract was missing here, causing the sync to either be skipped — with an error when syncing the new contract (OData) — or to already have taken place during the previous sync (CRM). This has now been fixed.

109712 | Error when syncing a Car Allocation from a flow

When syncing a Car Allocation from a flow, an error could occur if a flexible field based on a customer-added field was used. This has now been fixed.

109979 | CAO, wage table, scale and step were not always updated correctly when syncing to MSF

If only the CAO, wage table, scale or step of a placement was changed — without the function itself changing — the function was not included in the sync to MSF. As a result, the sync could fail and the old CAO, wage table, scale and step remained incorrectly in MSF. Function, scale and step are now always included in the sync to MSF, so this data is updated correctly.

110088 | Sync of payment data to MSF now only for a clear-cut record

When syncing payment data from a candidate from MSR, a record in MSF is now only updated if exactly one clear-cut record can be found there (or if no payment data exists yet). If MSF contains multiple accounts — for example with a start or end date, a fixed amount, or a different account holder name — the sync is no longer performed, and this must be adjusted manually in MSF.

Version 2.9.8

110215 | Manual wage was sent along with a wage classification on the employment contract

If a wage classification (wage table, wage scale and wage step) was set on the wage record of an employment contract, the manually entered wage was also sent to MSF during synchronisation. This could unintentionally clear the wage classification in MSF. From now on, the manual wage is no longer sent when a wage classification is present on the employment contract wage.

is.

Version 2.9.9

110298 | Sync of payment data to MSF now only for a clear-cut record

When syncing payment data from a candidate from MSR, a record in MSF is now only updated if exactly one clear-cut record can be found there (or if no payment data exists yet).

If a clear-cut record can be found next to a record with a fixed amount, the synchronization of the payment record will succeed.

However, if MSF contains multiple accounts — for example with a start or end date, a business unit, or a different account holder name — the sync is no longer performed, and this must be adjusted manually in MSF.

Version 2.9.11

111743 | Unclear error message when an IBAN could not be synced

When a personal bank account (IBAN) had been changed in MSF in fields that MSR does not manage, for example dates, changes from MSR could no longer be synced to that IBAN, and the error message did not explain why. As of now, the sync shows a clear message that the personal bank account (IBAN) was changed in MSF, so no changes can be made from MSR, and that you need to go to MSF to correct this.

Overview of this release

🔗 Find all features from this release here