For years Sage has required all batches to be posted before the database is upgraded. However, when asked why this needs to occur, I have yet to get an answer that justifies having this validation. All the data is stored in the database and anyone doing an upgrade will be doing a full back of the database before doing the upgrade in case of unforeseen issues.
If the upgrade works as designed, the pending batches should simply remain as they are. If there is a change in posting logic that would impact upgrading pending batches, I can see the reason behind the warning to post before upgrading. However, not much changes between versions in regards to posting, so this scenario should occur rarely. It's time to remove that validation if nothing in the Sage 500 posting logic impacts the existing pending batches.
by: Louis D. | over a year ago | 6 - General Enhancements
Comments
Ah, Lou, that was even before your time and was a reaction to an upgrade that caused corruption which required an emergency patch and expensive secondary release. That was back when the product was distributed on media and it was a support and logistical nightmare for a while (poor Ray and Agnes!). The most recent case in which I saw an absolute need for it was the 6.3 to 7.05 upgrade, but I require it just as a matter of habit because it helps us find and clean up errant data.