Version 9.1.254.4 (Support Release - 16 September 2026)

Imports

Resolve emails being sent out after User import of existing users (#154003)

Problem

• During user import, existing users are rebuilt as new DomainUser objects inside UpdateExistingUsers.
• The lookup model used for existing users did not include WelcomeNotificationSentDate, so the rebuilt object always had that property as null.
• That null value then flowed through the import response/update path, making it look like the user had never received the welcome notification and allowing the value to be reset or rematerialised incorrectly.

Solution

• The existing user lookup now reads WelcomeNotificationSentDate from [Account].[Users] and stores it on BasicUserPreviewPayrollModel.
• When UpdateExistingUsers reconstructs the existing DomainUser, it copies the saved welcome notification date back onto the object.
• The bulk update config also excludes WelcomeNotificationSentDate from updates, giving a second layer of protection so imports update user details without clearing the welcome notification history.
  

Corrected property to be excluded that is a normal column and not a ValueObject (#154003)

Problem

• Excluded properties are mapped within the SQL insert/update call, but for the sent welcome notification, it is identified as if it were nested within another object

Solution

• Added a fix to remove one part