MSR Combi Fixed Features 2026-04

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

CONTENT

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.