The lack of Beanworks ( Sage AP Automation ) support for Unified Login has become an increasingly sore spot for this customer. It causes them to question how modern Sage 100 is and even though they have a relatively small user count ( under 20 ) the use of Unified kept their Sage app in compliance password-wise.
I'm not really certain why the "trick" of disabling unified, creating a "regular" Sage user with password, then re-enabling unified and using that "regular" account with the Beanworks Sync isn't working. Unfortunately, the customer gets an error if they try to keep unified enabled.
Does anyone know who wrote the Beanworks sync? Or is that something they created internally?
------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------