MSR Combi Fixed Features 2026-1

INDEX

• 97719 | End date of wage and rate records when importing placement rates

• 97789 | “Copy work address” action no longer shows “null null” for empty address data

• 98002 | End date of original placement not correctly synchronised when cloning via flow

• 98483 | Project Resource batch report: error is now logged on the correct placement

• 97884 | Validation logic adjusted for “Apply Account Invoice Settings”

• 98603 | Amounts in wage data displayed correctly for Dutch language setting'

• 98744 | Incorrect sync error message resolved

• 99349 | Improved display of collective labour agreement (CLA) text

• 99489 | Interface Log now shows correct status when a synchronisation error occurs

• 100300 | XML fields rate, wage and collective agreement wage no longer missing from placement XML

• 100568 | Cost centres can again be selected when creating cost centre authorisations in Dutch

• 97828 | Option to end original placement when cloning is now correctly available

 

97719 | End date of wage and rate records when importing placement rates

When using the global action “Import new rates” in MSR, the same logic is now applied when creating new wage and rate records in MSR and synchronising them to MSF as is used when manually creating new placement details. In some cases, additional fields were synchronised to MSF unnecessarily. This has now been resolved.

97789 | “Copy work address” action no longer shows “null null” for empty address data

When using the “Copy work address” action on a placement detail and the linked project did not contain (complete) work address data, the result could previously be displayed incorrectly as “null null”. This has now been fixed. The action now correctly handles empty address fields, preventing invalid address values from being copied or displayed.

98002 | End date of original placement not correctly synchronised when cloning via flow

When a placement was cloned via a flow and the original placement was automatically ended, the updated end date of the original placement was not correctly synchronised to MSF. In MSF, the old end date remained visible, while the placement in MSR had already been ended with a new end date. This has now been corrected.

98483 | Project Resource batch report: error is now logged on the correct placement

When running the BCProjectResourceReportBatch, a validation error on a placement could result in an Apex Job Result being created with a link to an incorrect record. This made it difficult to identify which placement was actually causing the error.

This has been improved. The batch now logs errors against the correct placement, ensuring that the Apex Job Result refers to the appropriate record. Messages related to placements for which no Project Resource Report was found in MSF are also logged more clearly.

97884 | Validation logic adjusted for “Apply Account Invoice Settings”

Users can now clear the following invoice fields on projects when the “Apply Account Invoice Settings” checkbox is enabled:

• Invoice Collection Method

• Invoice Frequency

• Invoice Layout

• Payment Terms

• Block Invoice Posting

• Business Posting Group

• VAT Customer Posting Group

• Invoice Transfer Method

Reason for this change
When “Apply Account Invoice Settings” is enabled, the invoice settings from the account are used instead of the project settings. The previous validation caused a catch-22 situation: users could not enable the checkbox because the fields were filled, but could also not clear the fields while synchronisation was active. This situation has now been resolved.

98603 | Amounts in wage data displayed correctly for Dutch language setting

For users with the Dutch language setting, amounts in wage data were previously displayed incorrectly. In read mode, the decimal separator was missing, and in edit mode, amounts were shown with incorrect decimal placement and extra digits.

From now on, amounts in wage data are always displayed and edited correctly according to the Dutch number format, using a comma as the decimal separator.
Synchronisation with Mysolution Flex via Combi remains unchanged and continues to function correctly.

98744 | Incorrect sync error message resolved

In some cases, when setting up MSR–MSF synchronisation in a sandbox, the following message could incorrectly appear:
“This sandbox is connecting to a production environment of Mysolution Flex. This is not allowed.”
This issue has now been resolved.

99349 | Improved display of collective labour agreement (CLA) text

We identified differences in the HTML display of collective labour agreement texts between MSF and MSR. Several adjustments have been made to improve the readability of the text.

99489 | Interface Log now shows correct status when a synchronisation error occurs

During an MSR → MSF synchronisation, it could occur that an individual process failed while the Interface Log still showed status code 200 in the Status code field. This incorrectly suggested that the synchronisation was successful, even though part of it had failed. The Successful field was filled correctly.

This has now been improved. The Interface Log now shows the correct status code when an individual synchronisation step fails, making it immediately clear that the synchronisation was not fully successful and preventing confusion between the Successful and Status code fields.

100300 | XML fields rate, wage and collective agreement wage no longer missing from placement XML

Since the previous release, the fields rate, wage and collective agreement wage were no longer included in the XML when generating placement XML for document templates. This has now been fixed. These fields are again included when creating placement XML for document templates, provided that the Combi package is installed.

100568 | Cost centres can again be selected when creating cost centre authorisations in Dutch

When creating a Cost Centre Authorisation on a placement, cost centres were sometimes not shown even though they were available. This has now been resolved. Active cost centres are again correctly filtered and displayed.

97828 | Option to end original placement when cloning is now correctly available

When cloning a placement that already had an end date filled in, the option to end the original placement was not visible. This could cause an overlap when the new placement started before the end of the existing placement, without the user being able to resolve this in the cloning screen.

From now on, a notification is shown when the start date of the new placement is before or equal to the end date of the original placement. The user is then given the option to automatically end the original placement before the start date of the new placement. This ensures that an action is only requested when necessary and prevents overlap errors.