tag:infinitekind.tenderapp.com,2009-01-14:/discussions/moneydance-development/2473-importqifintoaccount-questionInfinite Kind: Discussion 2021-06-06T15:20:25Ztag:infinitekind.tenderapp.com,2009-01-14:Comment/473045942021-02-07T23:40:44Z2021-02-07T23:40:44ZimportQIFIntoAccount question<div><p>Ah yes, Python doesn't have this issue as it's not compiled, and just runs... Glad you have found it... (but yes, I do link the latest jar file into my IDE for code checking anyway)....</p></div>Stuart Beesley (Mr Toolbox)tag:infinitekind.tenderapp.com,2009-01-14:Comment/473045942021-03-07T02:48:21Z2021-03-07T02:48:21ZimportQIFIntoAccount question<div><p>Hi Stuart,<br>
Thanks for your work here. I've had a chance to give it a glance, but I think I'm still constrained by the importer. My QIF files have categories, and so far as I can see, the importer still insists that I may have categories imported OR confirmation blue dots, but not both.<br>
I really don't understand the logic behind that, but it appears insurmountable, or I've overlooked some option somewhere?<br>
Ultimately, I would like to be able to import my QIFs downloaded from my banks with the categories they already contain, and then run through the confirmation process to merge any already entered transactions <strong>without</strong> having all the categories reset to the default or to the "MD-knows-better-by-inferring-from-recent-value" during the confirmation. In other words, to use confirmation in my use-case, MD thinks it best to remove the <strong>correctly provided</strong> categories during the import and replace them with the default category, and then offer a somewhat randomly intelligent guess during the import. Groan.<br>
Does anyone know of a method to import QIF categories AND set the confirm flag?</p>
<p>I only download QIF files monthly, but I -mostly- enter sync transactions as I go, so there's a need to manually process and assess duplicates SUBJECTIVELY at month end. It can't be sensibly handled by Macro as suggested elsewhere by Kevin N. because the macro can't decide whether it's a dupe, entered to the wrong account, legitimate, or mis-dated, mis-categorised etc. Maybe there's some AI scope there, but I think we're not there yet and the whole confirmation process would be ideal if MD would allow me to use it purposefully by not killing my categories during the import! :-)<br>
Cheers,<br>
Tony</p></div>tgilbert666tag:infinitekind.tenderapp.com,2009-01-14:Comment/473045942021-03-07T14:45:46Z2021-03-07T14:47:02ZimportQIFIntoAccount question<div><p>.</p></div>Stuart Beesley (Mr Toolbox)tag:infinitekind.tenderapp.com,2009-01-14:Comment/473045942021-03-07T14:47:07Z2021-03-07T14:47:07ZimportQIFIntoAccount question<div><p>First part of response:</p>
<p>IMHO when you set the (bank) 'DOWNLOADED' flag then you get the full online txn functionally and match features; when you don't, you don't.. It's hardcoded deeeeep in the API.. I do not see how you can change this:</p>
<p>E.g. right at the very end before the record save....:</p>
<pre>
<code>If Bank DOWNLOADED
OnlineTxn olTxn = new OnlineTxn()
....
set all the ol.xxx parameter keys
....
setAccountWasUpdated(account, olTxn);
ELSE (if not bank downloaded)
txn.setParameter("qif.orig-txn", qifTxn.getOriginalLines());
eliminateDuplicatesAndAddTxn(txn, possibleDuplicate, txnSet);
return theTransaction</code>
</pre>
<p>You could post-process the txns and programmatically add the necessary keys, but I think this would be problematic and not a very future proofed solution......</p>
<p>Onto your related question.....</p></div>Stuart Beesley (Mr Toolbox)tag:infinitekind.tenderapp.com,2009-01-14:Comment/473045942021-03-07T15:10:49Z2021-03-07T15:10:49ZimportQIFIntoAccount question<div><p>So, perhaps some good news... I think I just did what you wanted.... If I understand you correctly, you want to be able to specify the category in the QIF file and import it such that the category is retained AND you get the online matching (blue dots) facility...</p>
<p>So, I used the field L in my qif</p>
<p>I set the L field to be exactly the same name/case as my existing Moneydance category.<br>
- e.g.</p>
<pre>
<code>LSTUART-CAT</code>
</pre>
<p>I used my demo_calling_import_functions.py script (v4).</p>
<p>I set:<br>
i_want_popups = True<br>
default_import_type = ImportDataSourceType.DOWNLOADED<br>
fileToImport="my file.qif"</p>
<p>Then I ran it. Selected DOWNLOADED.. Interestingly, MD wanted to override this and on the next normal import popup screen, the Downloaded field was NOT set. So I ticked it, and then ran the import.. Hey presto - a blue dot AND my category was set..</p>
<p>I suspect the pre-scan is overriding it.. If you play around with this (i.e. set it again after the pre-scan) you may get the headless mode to work the same....</p></div>Stuart Beesley (Mr Toolbox)