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 722996 - Cannot add stock price on Price Editor - Error: You must select a Security
Cannot add stock price on Price Editor - Error: You must select a Security
Status: RESOLVED FIXED
Product: GnuCash
Classification: Other
Component: Currency and Commodity
2.6.0
Other Windows
: Normal major
: ---
Assigned To: gnucash-core-maint
gnucash-core-maint
Depends on:
Blocks:
 
 
Reported: 2014-01-26 00:27 UTC by jfjunior
Modified: 2018-06-29 23:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Security detail dialog boxes and error message (94.53 KB, image/png)
2014-01-26 00:30 UTC, jfjunior
Details

Description jfjunior 2014-01-26 00:27:57 UTC
This is a new issue with version 2.6. Once I try to add a new price for my RY (RBC) shares (security) it comes up with "You must select a Security" error message. 

The only way I can add the price is by loading the file under version 2.4x of GNUCASH.
Comment 1 jfjunior 2014-01-26 00:30:05 UTC
Created attachment 267208 [details]
Security detail dialog boxes and error message
Comment 2 John Ralls 2014-01-26 01:16:03 UTC
Well, the problem is evident: A security can't be in namespace CURRENCY. If you somehow managed to get it there with an earlier version of GnuCash, use the Security Editor to put it in another one, either one of the supplied ones or one of your own making (but not "template"). In the US, RY trades in USD on the NYSE, but you're probably using the Toronto Stock Exchange so I'd suggest creating a namespace TSE and putting RY there.
Comment 3 jfjunior 2014-01-26 03:11:46 UTC
Thank you for pointing that out. 

I've no idea how the namespace changed to "Currency" as I had it setup as TSX since 2010. I double checked my other Investment account and confirmed they are ok - Namespace = Fund. 

I think something happened during upgrade. The most strange thing is that I could open it in the old version and it would work just fine. Oh well, I've changed the last 3 to TSX and deleted the old 108 RY quotes and all is working as it should.

Thanks again.
Comment 4 Philippe A 2016-02-13 18:35:49 UTC
There is really a bug. Some namespaces don't stick.
Here's what I see in 2.6.9.

In the securities editor, create a security new under NYSE:
full name U
symbol U
type : NYSE
click ok

Still in the same editor, select that security and click edit. All values will appear where appropriate.

Now create a new security under the TSX namespace.
full name: C
symbol: C
type: TSX
click ok

Select C in the list and click edit. The type field will be blank. Other values will be there.

This seems to have implications in the price editor as well.

In the price editor, add a price for U. Say it is yesterday's close.
Now you want to enter today's close.
What I typically do to save a few clicks is this:
- In the price editor, I drill down to NYSE->U.
- I click the first price in the list.
- Then I click the add button.
- The editor appears. Namespace will be set to 'NYSE', security will be set to 'U'. So I fill the rest.

Now do the same for C.
Add yesterday's close.
Then add today's close based on yesterday's.
Namespace will set to 'CURRENCY', security will be set to 'C'. 
You have to:
- Change the namespace to TSX
- Re-select the security. (unless it is the first in the list)
- Fill the remainder.

This is very annoying when you have to enter quotes manually. I do that every few month for many symbols. I don't pull quotes everyday.

Thanks.
Comment 5 Philippe A 2016-03-05 18:36:52 UTC
I have omitted to say that when you try to add a price for C and the namespace is set to CURRENCY, you will be given the exact same message OP mentioned.
Comment 6 John Ralls 2016-03-05 20:09:35 UTC
Yes, that part isn't a bug, though the error message could be more helpful. It's a two-key lookup (CURRENCY and C) and there's no match.

The actual problem here is that when you have a previous price highlighted when you click the Price Editor's add button the dialog box opens with all of the fields filled in, but the category field is filled in only if the category is one of the hardwired ones.
Comment 7 John Ralls 2016-03-08 23:22:00 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Once that release is available, you may want to check for a software upgrade provided by your Linux distribution.
Comment 8 John Ralls 2018-06-29 23:25:26 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=722996. Please update any external references or bookmarks.