QFX import problem and work around, possible bug or new feature?

[Chris Lyttle]

I had exactly the same issue and used the same work around to get it to 
import. I thought it might be an issue with libofx's parsing of the 
file. No clue what the fix is though.

Chris

On 9/2/2016 9:06 AM, gnucash_user wrote:
> All,
>
> Today tried to import data from a credit card account and found that 
> the description fields were showing as null rather than with the payee 
> value.
>
> Studied the QFX file and noticed that the format of a transaction 
> record as received from the provider has changed from:
>
> <STMTTRN>
> <TRNTYPE>DEBIT
> <DTPOSTED>xxxxxxxxxxxxxxxxx[0:GMT]
> <TRNAMT>xxxxx
> <FITID>xxxxxxxxxxxxxxxxxxxxxx
> <NAME>xxxxxxxxxxxxxxxxxxxxx
> </STMTTRN>
>
> to
>
> <STMTTRN>
> <TRNTYPE>DEBIT
> <DTPOSTED>xxxxxxxxxxxx[0:GMT]
> <TRNAMT>xxxxxxxxxxxxxx
> <FITID>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> <NAME>xxxxxxxxxxxxx
> <CATEGORY>
> <MEMO>null
> </STMTTRN>
>
> Note xxxxxxx represents the valid entries hidden for privacy reasons.
>
> Work around is it to delete the lines:
> <CATEGORY>
> <MEMO>null
> from the .QFX file from each transaction via your favorite text editor 
> or awk or sed script.  After removal, the file imports as expected.
>
>
> Is this a bug or new feature that needs to be reported or is it 
> already known?  Or is there another way to address this problem?
>
> Thanks
> Michael
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>