After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 796054 - unposting and reposting invoice doubles amounts
unposting and reposting invoice doubles amounts
Status: RESOLVED OBSOLETE
Product: GnuCash
Classification: Other
Component: Business
3.1
Other Windows
: Normal normal
: future
Assigned To: gnucash-core-maint
gnucash-core-maint
Depends on:
Blocks:
 
 
Reported: 2018-05-13 00:11 UTC by Phil Bowles
Modified: 2018-06-30 00:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Phil Bowles 2018-05-13 00:11:13 UTC
I've just upgraded from 2.6.19 to 3.1, using Windows client and MySQL back end.

Unposting and reposting an invoice or bill leaves additional records in the splits table, which causes the invoice to appear duplicated.

Additionally the invoice then becomes corrupt and cannot be unposted again. I needed to edit the raw tables in SQL to remove the offending records and the invoice as well.

Repeated the same steps twice on an invoice and a bill, with the same results.  I can confirm this doesn't occur in 2.6.19
Comment 1 Geert Janssens 2018-06-24 19:05:56 UTC
Thank you for your report. I have tried to reproduce this with the just released gnucash 3.2.

Aside from one register refresh glitch I haven't been able to reproduce this.
I can correctly unpost and repost invoices and bills. The always only appear once.

The glitch was early on when experimenting with a newly created book in which I didn't have an A/P yet and that had to be saved to mysql starting from sqlite3. At some point one invoice transaction seemed to remain in the A/P account regardless of whether I unposted and reposted the invoice (upon reposting a second entry appeared). Closing the register and opening it again cleared the issue.

I will note I didn't find a mysql db created during 2.6 that I could open in 3.2. Can you retry this on (a copy of) your book with 3.2 ? Or attach a db dump of a small mysql based book that shows the bad behaviour ?

Thanks.
Comment 2 Geert Janssens 2018-06-24 19:10:43 UTC
Ehr, "just released" is a tad premature. The 3.2 release is ongoing right now and should be there one of the next days. Please test when it's there or with a recent nightly build.

Also I couldn't test on Windows, I can only say it works on linux.
Comment 3 John Ralls 2018-06-30 00:09:53 UTC
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=796054. Please continue processing the bug there and please update any external references or bookmarks.