Thank you all; having considered all feedback, there will be an upcoming 3.10 with the old reconcile behaviour reverted.
I agree that this "fix", although correct in principle, was premature because it could not handle invalid data. The reason I feel/felt that rollback this "fix" and to tolerate invalid data (without a book property or a book feature) is highlighted exactly by David Carlson's opinion: if old data was not consistently precise in requiring accurate reconciliation statement dates, it could mean that fixing reconciliation dates safely is practically impossible; I do not think there is a safe one-time scrubbing mechanism (either silently as are other scrubs in existence, or UI-driven) which is guaranteed to work well. With a book property/feature approach, a natural progression of this "fix" is that reconciled dates & balances *will* be stored and can a data-integrity check be re-run anytime, thereby providing reconciled balance assertions. But this will be reserved for a future time. So, 3.10 is planned for this weekend. On Fri, 10 Apr 2020 at 01:02, David Carlson <david.carlson....@gmail.com> wrote: > Some users like me did a lot of mis-managed reconciling while importing old > data into currently used accounts and just reconciling years of > transactions as of the current month instead of trying to obsessively go > back years and assign the transactions to years-old statements, especially > when reconcile dates cannot be viewed in the UI. While I doubt that we > would want to correct those old transactions, if reconcile dates would > somehow become visible sometime in the future, we might need to > occasionally find and fix some transactions here and there, especially if > they had been re-reconciled to the wrong month after an edit erroneously > un-reconciled them. > > On Thu, Apr 9, 2020 at 7:30 PM David Cousens <davidcous...@bigpond.com> > wrote: > > > David T. > > > > Yes I did correct and eliminate the problem by editing the data file > > directly and I also agree this is not really viable for the average > user. I > > only had one incorrectly entered date in one account and for users who > have > > many years of data the situation could be considerably more complex. I > also > > had external information about when I had performed past reconcilaitions > so > > my fix was a simple search and replace once I had verified that it was a > > single reconciliation date and the splits which were incorrect agreed > with > > the date I suspected should have been entered. > > > > I made some suggestions in the DEV forum in response to Chris's options > for > > a way forward by making the feature optional which may allow the feature > to > > be retained but switched off by default in preexisting datafiles and only > > switched on by default in new data files that may allow retention of the > > feature with no disruption for user's with files which may have wrong > past > > reconciliation dates. It obviously depends on how easy the changes needed > > to > > implement that are. > > > > Another user has raised a separate issue which seems to be associated > with > > a > > different startup of the reconciliation process automatically when using > > AQbanking to import balances which may or may not be related. He has > raised > > a separate bug report and I have closed the one I raised as resolved. > > > > David Cousens > > > > > > > > ----- > > David Cousens > > -- > > Sent from: > http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html > > _______________________________________________ > > gnucash-user mailing list > > gnucash-u...@gnucash.org > > To update your subscription preferences or to unsubscribe: > > https://lists.gnucash.org/mailman/listinfo/gnucash-user > > If you are using Nabble or Gmane, please see > > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > > ----- > > Please remember to CC this list on all your replies. > > You can do this by using Reply-To-List or Reply-All. > > > > > -- > David Carlson > _______________________________________________ > gnucash-user mailing list > gnucash-u...@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
