Hi Geert- The intro screen DOES mention the namespace requirement in 3.6, I just didn’t stop to read it until I found the bug report. It didn’t in 3.5 and once I got my import working, I stopped reading it.
It was trivial to update my script, but (please forgive my after-the-fact questioning) wouldn’t it have been cleaner to set a flag for the whole file to distinguish between currencies and other asset types instead of requiring the user to add the namespace to each record? In other words, is there a normal use case for importing both currencies and other assets in the same file? Robin On Sun, Jul 7, 2019 at 3:42 PM Geert Janssens <[email protected]> wrote: > Op zaterdag 6 juli 2019 23:06:56 CEST schreef Robin Chattopadhyay: > > Hi Art- > > > > I found this Bug that was fixed in 3.6 that is the source of the new > > Namespace requirement. https://bugs.gnucash.org/show_bug.cgi?id=797278 > > > > You're right, the intro screen to the import does now mention the need > for > > the Namespace field. > > That bit is worth a bug report on its own. Can you submit one ? > > Thank you, > > Geert > > > -- --- Typed with my thumbs and sent from my iPad. _______________________________________________ gnucash-user mailing list [email protected] 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.
