Includes db changes. You need to log all terminals out during upgrade

Bugfix with General Ledger cache changes

Recent changes to GL cache contain a bug. Certain narrow combinations of behaviour can invalidate the cache resulting in incorrect general ledger balances being presented. Underlying cause is fixed here. Following is two scenarios that can trigger issue

• add a factory unit on floorplan. 24 hours or more later modify that unit so it is a straight purchase ( or vice versa)
• create a job with an invoiced sublet. 24 hours later, delete the sublet.

The underlying bug is older than recent changes actually. Cache invalidation is supposed to happen whenever gl changing modification is detected. But a couple of types of txns, mainly tax coding changes (like. switching from to/floorplan) and changes to reserve tracking (e.g. sublets on open jobs)where not invalidating cache. In prior c9 cache, other simultaneous changes would also happen that invalidate the cache anyway. But the new cache algorithm is a lot more surgical/efficient in what gets invalidated; making a previously masked problem now obvious.

Part of changes to gl cache we added daily tests and alerts to verify cache is accurate; which is how we detected this issue so quickly. This test has been refined in this version to also automatically force a complete rebuild of the cache.