Skip to content
This repository has been archived by the owner on May 8, 2018. It is now read-only.

QIF files whith !Type:Invst not working #3

Open
vandersonmota opened this issue Dec 8, 2010 · 7 comments
Open

QIF files whith !Type:Invst not working #3

vandersonmota opened this issue Dec 8, 2010 · 7 comments

Comments

@vandersonmota
Copy link
Contributor

I tested many QIF files with !Type:Invst, but i always get this traceback:
Parse exception during 'QIF' conversion:
Expected '!Type:CCard' (at char 0), (line:1, col:1)

Here is one of the files:
!Type:Invst
D6/11'06
T18,000.00
NShrsIn
YCesp
I18
Q1,000
^
D22/11'06
T13,000.00
NShrsOut
YCesp
I26
Q500
LRendimento de investimento:Ganhos de capital
^

@precipice
Copy link
Member

Hm, that's entirely possible. I'll take a look.

@precipice
Copy link
Member

One of the problems is that the Date value is tacked onto the end of the transaction start line. I'm not tackling that part right now - you can fix that by changing:

!Type:Invst D6/11'06

to read instead:

!Type:Invst 
D6/11'06

and likewise, changing:

^ D22/11'06

to read instead:

^
D22/11'06

The rest of the file parses correctly with a small change, but it spits out the wrong OFX format (it produces a bank statement instead of an investment statement). I'll look at fixing that now.

@precipice
Copy link
Member

See commit 176d035. The parse exception no longer occurs, but I haven't added investment support yet, so the document is instead returned as a bank statement. That may be enough in some sense, but if not, you could add investment support yourself and send a pull request. I may get to it later or someone else may, too.

@vandersonmota
Copy link
Contributor Author

I already fixed it. We made the same commit. =)
myfreecomm@af5ff9f

@precipice
Copy link
Member

Heh, okay. Update the issue! :)

Looks like you have a lot of commits going in. If they're generally valuable and you want to make a pull request I'll look them over.

Thanks.

@vandersonmota
Copy link
Contributor Author

Everything's ok now. I'll make an review and send a pull request.

Cheers!

@precipice
Copy link
Member

I reopened the bug since as far as I know neither our fixofx nor your fork are yet generating correct OFX investment statements. Please correct me if I'm wrong. :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants