Re: [GNC] Error running Advanced Portfolio report

[Dino Carubia via gnucash-user]

 Nevermind... figured it out.  Found a transaction from 2011 that was the 
culprit.  This issue did not happen in older 2.x versions of GNUCash where 
transaction was entered,  so it must be a feature of 3.x versions!  :-)
To solve this issue, use edit/find to look for a transaction with shares equal 
to whatever GNUCash tells you in the error message.  Review results and look 
for cases where the 2nd to last transaction balance entry goes to 0 and then 
the last transaction balance entry goes negative.   In my case the dates were 
the same for the transaction so I just made the last transaction date one day 
earlier and the report started working.
Thanks to the dev team for a clear error message!
Regards
    On Sunday, January 5, 2020, 05:31:03 PM EST, Dino Carubia 
<dcaru...@yahoo.com> wrote:  
 
 I'm using GnuCash Version 3.7.  When I run the Advanced Portfolio report, it 
processes for a bit, then it stops and I get a partial report with an error 
message: "There is an error processing the transaction 'buying .0030 share 
units'. This may to be caused by a sell transaction causing a negative stock 
balance, and a subsequent buy transaction causing a zero balance. This leads to 
a division-by-zero error. It can be fixed by preventing negative stock 
balances."
I have searched for a transaction where I am buying .0030 shares and cannot 
find it.
Is this a known bug or a "feature" of 3.7?  Why does the order of negative and 
positive stock balances matter when processing this report?
Any help would be appreciated, thanks!
Regards
  
_______________________________________________
gnucash-user mailing list
gnucash-user@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.