Sage 100

**Hey Sage HRMS Big Dog Gurus** I upgraded client from v2015 to v2017 last week. Would have gone to v2018 but they have PR and I am not looking for trouble with over 200 employees to fret about. They also run Sage HRMS and there seems to be some confusion with their HRMS consultant on whether the HRMS link with Sage 100 v2017 works without major issue. Below is what I was sent from client. _I think SQL and it is 2016 a ""no longer supported"" version. My consultant said no hurry on updating to 2017 since we don't use a lot of the options. He said he had another group that updated to Sage 2017 (he does nothing with Sage just HRMS) and then had issues when an employee worked SD and then changed to IA and things were getting messed up on just certain employees with SUI and possibly state wages and first they thought it was something with the link and then it finally was determined it was a problem in Sage 2017 payroll and this place I guess has a work around but it isn't a Sage fix..Sage's fix was update to 2018 which is crap!! I told him to try to send me more specifics on it as I wasn't quite understanding all the issues._ Any thoughts which clarify are very much appreciated.

Jeff, our HRMS consultant response: ""see[ms to be] a couple different questions here, but as far as the Sage 100/Sage HRMS link, there was an issue when HRMS 2017 was first released regarding wages transferring. But, they fixed it in a service release. I have seen no other wage issues regarding the Sage 100 link."" Also, noteworthy is that there is no version 2018 for HRMS, 2017 is the latest.

Thanks for the feedback. Will pass it along. I believe the v2018 reference was for Sage 100.

@MichelleTaylor1 - From my client - _Yes I know there isn't a 2018 version of HRMS so I don't know where that is coming from Sage said the fix is to install 2018 of Sage 100 as they have removed some of the ""linked"" field in 2018 Sage 100 which is the fix. I still am not comfortable upgrading when there is a known issue but doesn't seem to be published. I guess I will reach out to the person again._

There's no a lot of experience with Sage 100 2018 with the link. There is only one customer that has 2018 AND the link; they did have a similar sounding issue and it was corrected with the Service Release in January. Sounds like Sage just isn't going to issue an update to address the problem in the other version, which we've seen before.