Yes.  There was a change.  Below is a list of the fields we had to update to a default value for clients.  The issue is usually a result of the initial import of information into Sage HRMS, whether pushed from Sage 100 (the onetime push of Employee Information from 100 to HRMS HR) or an import via Sage HRMS Link that did not include these fields.  You can run a SQL script to first search for any blank values on these fields.  Then you can mass update to the Default.  The defaults for the last three are "N".  The other four have the default.  Hope this helps.

Most appreciate the info and quick reply!!!

Allison, do you know how this was documented by Sage and how Partners got notice of this?

I do not.  I think there may be a KB article on the issue.  We discovered soon after the Q2, 2024 update and determined the fields by the Sage 100 Error Log and a ticket with Sage Support.  As far as I know there was no specific notification to Partners of an issue.

I do not.  I think there may be a KB article on the issue.  We discovered soon after the Q2, 2024 update and determined the fields by the Sage 100 Error Log and a ticket with Sage Support.  As far as I know there was no specific notification to Partners of an issue.