Registered Member
|
Hello,
Since a couple of week filters are not applied when I'm importing ofx bank file. Import lower right corner progress bar told me filtering is applied but there is absolutely not category applied on operation. When I do apply rules for search an filter tab it's worked well. I modified global setting to set or unset this function in import/export tab but same issue. I've tried to modify character from Utf8 to CP1252 in the import window. Here is the beginning of the Ofx file: FXHEADER:100 DATA:OFXSGML VERSION:102 SECURITY:NONE ENCODING:USASCII CHARSET:1252 COMPRESSION:NONE OLDFILEUID:NONE NEWFILEUID:NONE I'm using skrooge 2.9 Any help is warm welcomed ! |
Moderator
|
Hi,
Take care, the rules are applied ONLY on the operations imported by the current import, NOT on all imported operations. This could explain why you have a different behavior when you apply the rules manually. Regards. |
Registered Member
|
Thank you Stephane for your help,
So this is my case as rules are not applied for current import. I download file from my bank using boobank then I import this file to Skrooge. |
Moderator
|
Do you know that if you use the "weboob" backend (see import settings), Skrooge is able to import automatically your accounts by using boobank?
Could you try it and tell me if you still have the issue? Regards. |
Registered Member
|
By the way I use Weboob out of the let's says Skrooge box.
Here is my command: --> boobank history 12345@creditmutuel --condition "date>2017-10-20" --count=100 -f ofx > /home/jpm/Téléchargements/Banks/creditmutuel.ofx |
Registered Member
|
I 've unsuccessfully tried to use weeboob with the embedded skrooge engine as the syntax is unclear for me.
I always get "Ce mode d'importation WEBOOB n'est pas encore implementé" Weboob is stored at : /home/jpm/.local/share/weboob/modules/1.3/ on my linux machine |
Moderator
|
Hi,
To enable, weboob backend, you just have to set "weboob" in settings like in this screen capture: And call "File / Import / Import with backends". PS: You can have some operation duplicated because operation imported from OFX files and operations imported with backends don't have same unique identifier. Regards. |
Registered Member
|
Solved !
This was caused by rules order.The last one "remove" previous categories assignation. Thank you for your help |
Registered users: bancha, Bing [Bot], Evergrowing, Google [Bot], mesutakcan, Sogou [Bot]