> On Apr 26, 2020 w18d117, at 7:28 PM, flywire <flywi...@gmail.com> wrote:
> 
> @Tom Seesink - Will you log that as an enhancement bug at
> https://bugs.gnucash.org/enter_bug.cgi?product=GnuCash (Import - other)?
> Please link back here.
> 
> @David Cousens, that excellent explanation about how the Import Matcher
> works helps answer my question. The documentation needs to explain
> the match is GUIDs rather than Transfer Accounts like other
> financial software.

Do you know other (including closed source) apps don’t use something similar? 
Why would a user normally need to know this implementation detail? If the 
import is done in small chunks, as advised (rather than one giant import with 
thousands of transactions) then the method behind the scenes isn’t an issue. Of 
course, GnuCash is open source, so anyone can go see for themselves that GUIDs 
are used without that fact being put in the docs.


> 
> An enhancement bug fix will take too long. Is there any way of getting
> GUIDs on the data? Perhaps reformatting it to QIF or OFX? Ultimately it is
> stored in a table somewhere. Is the code the only place to find the details
> on the import process?

There are many threads on this list discussing the process. Also, bugs which 
were addressed by the changes will have some discussion in them.

Until the docs are updated, this would be the only source of info other than 
the code itself.

Regards,
Adrien
_______________________________________________
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.

Reply via email to