Bug #98470 for Finance-QIF: QIF-3.02 missing support present in QIF-2.04

Sat Aug 30 15:50:21 2014 dhdurgee [...] verizon.net - Ticket created

Subject:	QIF-3.02 missing support present in QIF-2.04
Date:	Sat, 30 Aug 2014 15:50:04 -0400
To:	bug-Finance-QIF [...] rt.cpan.org
From:	"David H. Durgee" <dhdurgee [...] verizon.net>

I have been using your 2.04 release with a routine, csv2qif, to convert the csv files I download from CheckFreeWeb for import to Quicken Deluxe 98 for Windows running in wine on my system on the previous linux release. I just installed the latest linux mint release and had to reinstall packages at the current level of service. When I attempted to use the csv2qif routine for the first time today I received the following error: dhdurgee@DHD-Z560 ~/Downloads $ csv2qif -f qk40830.csv Unsupported field 'amount' found in record ignored in file '>write.qif' line 2 at /home/dhdurgee/bin/csv2qif line 35. Unsupported field 'amount' found in record ignored in file '>write.qif' line 6 at /home/dhdurgee/bin/csv2qif line 35. Unsupported field 'amount' found in record ignored in file '>write.qif' line 10 at /home/dhdurgee/bin/csv2qif line 35. Unsupported field 'amount' found in record ignored in file '>write.qif' line 14 at /home/dhdurgee/bin/csv2qif line 35. After a bit of thought, I tracked down QIF.pm on both installations and found that 3.02 has: "T" => "transaction", While 2.04 has: "T" => "amount", I went ahead and added a line to QIF.pm after the current line: "T" => "amount", # match download from CheckFree This appears to have corrected the problem. I did this only in the noninvestment section, as the csv files from CheckFreeWeb is for bill payments and my routine thus is for Type:Bank records. You might want to consider if this is an appropriate edit for your next release. Dave

Fri Sep 12 01:18:37 2014 mmcgillis [...] cpan.org - Taken

Fri Sep 12 01:22:04 2014 mmcgillis [...] cpan.org - Correspondence added

The change was intentional your script needs to be properly updated for the changes between 2.x and 3.x this note in the change log should help to guide you with modifications. 3.00 Thu Jul 24 12:17:00 2008 - Added support for Quicken 2006 new Memorized Investment fields - Added support for Quicken 2006 Price format - The changes for the Memorized investment created a conflict with naming to get things consistent and to hopefully avoid future issues some value names have changed. This is the reason for a 3.00. Old code may require modification this map will help in porting Old Name New Name noninvestment:amount noninvestment:transaction memorized:transaction memorized:type memorized:amount memorized:transaction

Fri Sep 12 01:22:05 2014 The RT System itself - Status changed from 'new' to 'open'

Fri Sep 12 01:22:05 2014 mmcgillis [...] cpan.org - Status changed from 'open' to 'rejected'

Fri Sep 12 07:55:29 2014 dhdurgee [...] verizon.net - Correspondence added

Subject:	Re: [rt.cpan.org #98470] QIF-3.02 missing support present in QIF-2.04
Date:	Fri, 12 Sep 2014 07:55:10 -0400
To:	bug-Finance-QIF [...] rt.cpan.org
From:	"David H. Durgee" <dhdurgee [...] verizon.net>

Matthew McGillis via RT wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=98470 > > > The change was intentional your script needs to be properly updated for the changes between 2.x and 3.x this note in the change log should help to guide you with modifications. > > 3.00 Thu Jul 24 12:17:00 2008 > - Added support for Quicken 2006 new Memorized Investment fields > - Added support for Quicken 2006 Price format > - The changes for the Memorized investment created a conflict with > naming to get things consistent and to hopefully avoid future > issues some value names have changed. This is the reason for a 3.00. > Old code may require modification this map will help in porting > Old Name New Name > noninvestment:amount noninvestment:transaction > memorized:transaction memorized:type > memorized:amount memorized:transaction

I am not the one preparing the .CSV file that I am using your package to convert to a .QIF file for import to Quicken Deluxe 98 running via wine on my linux system. Therefore I have no control over what CheckFreeWeb chooses to label their columns. All I knew is that things were working properly with your 2.04 version and worked no longer with the 3.02 version. I assume that your module is designed primarily to facilitate manipulating QIF files and that the use I am making of it to create a QIF file from a CSV is a secondary use. I should note that I am not the only one doing such conversions, as I was able to locate and use this script for several years on my older installation. As I noted in my original message, I was able to deal with this situation by adding a single line to your module to support the "amount" column in the CSV records as an alternative to "transaction" you are expecting. Could this be added as an "alternative label" of some sort with "amount" still being recognized for input from foreign formats as equivalent to "transaction" for that purpose only? Thank you for your consideration of this issue. David H. Durgee

Fri Sep 12 12:20:23 2014 mmcgillis [...] cpan.org - Correspondence added

Show quoted text

> All I knew is that things were working properly with your > 2.04 version and worked no longer with the 3.02 version.

Agree see above comment as to why. Show quoted text

> Could this be added as an "alternative label" of some sort > with "amount" still being recognized for input from foreign > formats as equivalent to "transaction" for that purpose > only?

Clearly it can be as you have done it and you are happy with the results, and that is great. However I reviewed the code and don't see this as a good idea. QIF doesn't know names that is an abstraction I added to make things more understandable for users. All QIF knows is one letter representations of values. In 2.04 some letters had different labels which was confusing. In 3.0 the letters got labeled consistently and that is a good thing. It certainly doesn't have to be this way. The letters can be what ever you like but in the 3.0 code the "T" value is always "transaction" and the "$" value is always "amount". If you mix things or replace things then it becomes unclear to me what is "T" and what is "$". Hope that helps.