from_date greater than 3 years ago gives initially displayed transactions and does not create an error. about dkb-visa HOT 4 OPEN

Hm, I am not sure I understand. A quick test revealed that changing the from_date does work for me. I guess there may be DKB-side limits how long you can go back in time...?
So, either I misunderstand or there must be some other difference between your test and mine. :)

Regarding the HTTPS-enforcement: As the URL is hardcoded and not user-changable, I think it is OK to leave it as-is.

from dkb-visa.

Ok, now I see -- the web interface only returns about one year of data, if I see it correctly. Yes, this is a limitation, but I do not see any way to overcome this besides integrating locally "archived" data.

from dkb-visa.

well, at least the error handling could be improved on the side of dkb-visa. If I set 01.01.1970 in the current version and submit, the UI automatically sets to the first date possible, 01.06.2015, and tells with a popup field: "Die Eingabe wurde systemseitig angepasst."

from dkb-visa.

Yes, that is the behaviour I ment: dkb falls back to the date where you
they have data. So the user of the script should be informed that they
don't get what they asked for.

Just FYI: In my fork I set the based on todays date minus two years and 11 months.
that way I get all the transactions. Then I wrote some code to
deduplicate the transactions.

Excerpts from Oliver Kurz's message of 2016-05-29 23:01:30 -0700:

well, at least the error handling could be improved on the side of dkb-visa. If I set 01.01.1970 in the current version and submit, the UI automatically sets to the first date possible, 01.06.2015, and tells with a popup field: "Die Eingabe wurde systemseitig angepasst."

---

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#7 (comment)

from dkb-visa.