Looks like that's the workaround:

Sage 100 Engineering shows this issue to be corrected on the following versions:

Sage 100 2017 Update 4 and higher

Sage 100 2018 Update 1 and higher and

Sage 100 2019 and higher.

If you are still experiencing the issue on any of the versions listed above, please contact support. 

It appears the Knowledge Base article was not updated, we will work to correct that. 

Thank You! Yes we are in an 2016 version. Unfortunately we have outgrown our system and are switching out.