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 728999 - Scheduled transaction creates lines with empty amount
Scheduled transaction creates lines with empty amount
Status: RESOLVED DUPLICATE of bug 736703
Product: GnuCash
Classification: Other
Component: Backend - SQL
2.6.3
Other Linux
: Normal major
: ---
Assigned To: gnucash-core-maint
gnucash-core-maint
Depends on:
Blocks:
 
 
Reported: 2014-04-26 05:54 UTC by Artiom MOLCHANOV
Modified: 2018-06-29 23:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
db grid (46.67 KB, image/png)
2014-04-26 05:54 UTC, Artiom MOLCHANOV
Details

Description Artiom MOLCHANOV 2014-04-26 05:54:38 UTC
Created attachment 275190 [details]
db grid

Sometimes random scheduled transactions create lines with an empty amount. I am using pgsql database, if I look at the splits table I see that there is a value in value_num column and 0 in quantity_num. See attaches screen with another good transaction aside.
Comment 1 John Ralls 2014-06-03 20:46:53 UTC
What is the SX template transaction that creates the bad transaction, and did it also create the good transaction?
Comment 2 Artiom MOLCHANOV 2014-06-04 07:37:51 UTC
All scheduled transactions create good and bad ones. I have done more investigation on it and I found that bad transactions have GBP currency while all my accounts are in EUR (default currency in settings is EUR). 
Another observation is that these transactions (in GBP) are not editable. This means that if I type a new value it is impossible to leave the line. No errors are visible in log either. The only way to end it is to close the account tab.
It is still possible to delete a bad transaction.
GBP could be explained by my locale (en_GB), but I suppose that at least default currency from settings should take precedence.
By the way is there a way to see transaction's currency from Gnucash? I can only see it directly in database.
Comment 3 John Ralls 2014-06-08 23:48:05 UTC
This sounds like it's the same as Bug 731019 and maybe Bug 723524.

Do you have accounts in GBP? Are any of them involved in the SXes that cause the problem? Are any of the defective transactions carried over from 2.4? Are any of them from 2.6? 

No, there's nothing that exposes the transaction currency to the GUI AFAIK. You can probably fix the defective ones with an update query, changing the transactions.currency_guid field to the commodity.guid for EUR. The report of 731019 was able to fix his similar problem in the XML backend that way.
Comment 4 Artiom MOLCHANOV 2014-06-10 08:03:31 UTC
I have no accounts in GBP, so I was surprised to find some GBP transactions. Surely I was able to fix it in backend, but what I want is to stop them being created.
Scheduled transactions which create defective transaction could be from 2.4, but defective transactions themselves were created now, by 2.6. I remember even to recreate some SXs (is this scheduled transactions acronym?) but it didn't prevent them to create defective lines.
I could imagine that then I create a SX with default currency set to GBP it creates transactions in GBP regardless on the account's currency. Is it possible? How can I check SXs currency?
Comment 5 John Ralls 2014-09-30 19:03:06 UTC
I think this is a duplicate of bug 736703. SXs are created in the default currency -- the one set on the Account tab in Preferences.

Because the amount is set to 0, the exchange rate isn't editable in either participating account window, but it is editable in find results and general ledger windows.

The fix for 736703 prevents SXs from creating 0 amount splits in currency accounts. That fix is in 2.6.4.

*** This bug has been marked as a duplicate of bug 736703 ***
Comment 6 John Ralls 2018-06-29 23:30:24 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=728999. Please update any external references or bookmarks.