I’ll start the list:
1. In place upgrade - or fix the process so we don’t need to do multiple workstation setups. Don’t pop up a “ now updating workstation setup” which may not complete due to security restrictions.
Customers have people working everywhere these days. In some cases we upgrade an office workstation, an RDP workstation ( sometimes multiple RDP servers ).
If I could I’d create a central ini file that the workstations all loaded Sage from so I could change the location of the new Sage - similar to the way Advanced manages servers.
After 20 years can’t someone figure out how to avoid loading local stuff on the workstations so that Sage can run? How have great SaaS companies managed this?
2. Something has to happen with integrated solutions - perhaps have those who are “Sage endorsed” also adhere to Sage’s coding so they don’t break during upgrades or have some way to warn that an update is about to break the integration.
This is definitely my #2 issue. Sage has driven off all the GLAPAR/no enhancement types . Now my typical customer is wholesale with 3-5 enhancements. These are tough to upgrade within a year of Sage’s release because we wait 6 months for Sage’s PU then another 3 for the integration.
We need attention to this area beyond just figuring out which enhancements throw off the most $$$.
3. Standardize the paperless location so each update or server move doesn’t require time consuming “re-pointing” to a new path.
---------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
---------------------------------