We upgraded to SQL driven Sage Estimating 18.12 this past December with a promise that with the product converting from PSQL to SQL, we will have a more efficient system. For the most part we have found this to be true. The one biggest complaint we have is we use JC transfer to our Sage 300 Accounting system. We found that the migrated estimates did not keep and hold the JC code formatting. We are now left to not only go through all the codes and correct the formatting in the database, which we have already spent over 2 days (and still currently going) fixing and updating all the code formats. We also learned that any existing estimates prior to the formatting change will also have to be manually updated with these codes. Over and above that, we have many years of past estimates dating back to 2010 that will require this manual process. I can't imagine that this side effect, for the lack of a better term, wasn't known prior to the time this version was released. Worse yet, I found nothing written that provided a warning about this side effect prior to upgrading. I also cannot imagine that this has not come up as an issue for other companies that went through a similar upgrade path that we did in our company. I believe it is incumbent upon the Sage Estimating Product Development team to come up with a process, maybe a SQL script, than can automate this formatting change. Many hours of work has already been investing in this effort and we aren't even close to being completed.

by: Ray B. | over a year ago | Other