[GNC] GC 3.2 Import Price File CSV

[Deva -]

Hmmm… Other than what Sebastien suggested, one other thing I can think of is to delete the commodity in your gnucash datafile and recreate it.

Perhaps you can try what I did. Just create a new blank datafile and setup this single security of ABF.L for testing. You don’t need any accounts as such. Then import and see what happens. If that works, then something in your main datafile is inconsistent with the import definition.

Do you have multiple definitions of accounts using ABF.L security or multiple definitions of ABF.L itself setup in different namespaces (perhaps for different brokerage accounts)? Not sure why that would cause a problem, but if the test datafile with a single definition works, then that might be an area to look at.

Since you are using m-d-y for dates, is your locale still UK or some other? Reason I ask is because your security currency is GBP, but if your locale is set to imply some other, then that might be causing a problem.

Sorry, grasping at straws here! Wish I could be of better help…

Cheers.

On 18-Aug-2018, at 8:04 PM, gnucash-user-request at gnucash.org<mailto:gnucash-user-request at gnucash.org> wrote:

Date: Sat, 18 Aug 2018 10:35:02 +0200
From: S?bastien de Menten <sdementen at gmail.com<mailto:sdementen at gmail.com>>
To: Megagrumpy <megagrumpy at hotmail.com<mailto:megagrumpy at hotmail.com>>
Cc: Gnucash userlist <gnucash-user at gnucash.org<mailto:gnucash-user at gnucash.org>>
Subject: Re: [GNC] GC 3.2 Import Price File CSV
Message-ID:
<CAB2pxDuXSXxjP71WkFBqoWnBAgW_wQsLDz24ssj32M3PRHXcnQ at mail.gmail.com<mailto:CAB2pxDuXSXxjP71WkFBqoWnBAgW_wQsLDz24ssj32M3PRHXcnQ at mail.gmail.com>>
Content-Type: text/plain; charset="UTF-8"

Would it be possible you have a blank as first character in your security
editor (i.e. " ABF.L")? The screenshot you sent give me this impression...
But it may be just a visual artifact.

On Sat, Aug 18, 2018, 08:54 Megagrumpy <megagrumpy at hotmail.com<mailto:megagrumpy at hotmail.com>> wrote:

Thanks for the response, Deva. I have tried every combination of date
format,
and security ID with no luck. Unfortunately my screenshots were taken from
different times so I agree - if I had tried to use those particular
settings
I would have had an error.  I have followed your instructions to the letter
and still I get the message "Commodity From could not be understood"! In
this case I have used the MDY date format. my input file reads:
ABF.L,08/12/2018,25,GBP

My commodity in the security editor is defined as ABF.L - see Scrrebshot:
<http://gnucash.1415818.n4.nabble.com/file/t377722/ABF_Security_Editor.jpg>


I still get the same error and it is only that the security ABF.L cannot be
recognised - see Screenshot:

<
http://gnucash.1415818.n4.nabble.com/file/t377722/ABF_error_screenshot.jpg>


As you can see the date and all the other fields are OK and parse
successfully. Only the Stock ID is rejected.





--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
_______________________________________________
gnucash-user mailing list
gnucash-user at gnucash.org<mailto:gnucash-user at 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.