On Apr 6, 2012, at 1:08 PM, Christian Stimming wrote: > > As for the data format for importing transactions: I'd agree with the > reservations about QIF as a data format. It has some severe limitations, > which > are somewhat worked around by the existing gnucash importer, but if you're > implementing a new importing scheme anyway, you should better choose an > exchange data format that doesn't give your obstacles from start on. Instead, > I'd rather suggest OFX as a data format. Hendrik mentioned a "unique > transaction identifier" that should be included in the exchange data format > for sure, and he is right. OFX has such a unique ID. It is being evaluated in > gnucash's OFX importer under the name "online-id". In fact, if the imported > file contains this field, duplicate transactions (whose online-id has been > observed in earlier imports) will be ignored from the import altogether right > now already. Hence, please try to use OFX' data format as your exchange data > format for transactions, if possible.
Christian, Doesn't this apply to Ngewi's app as well? In fact, aren't these essentially the same project implemented on two different mobile OSes? Regards, John Ralls _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
