Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pushing to deleted accounts should be disabled/optional #52

Open
chbndrhnns opened this issue Aug 11, 2017 · 2 comments
Open

Pushing to deleted accounts should be disabled/optional #52

chbndrhnns opened this issue Aug 11, 2017 · 2 comments

Comments

@chbndrhnns
Copy link

Steps:

  1. connect to account, chose existing budget, push something
  2. delete budget in web interface
  3. push same data again

Expected result:
pynYNAB does not sync deleted budgets by default.

Actual result:
The data is recognized as duplicates.

@rienafairefr
Copy link
Owner

I'm interested to see how the android app behaves in this same case. YNBA servers should probably reject modified entities that apply to a missing budget, I think...

What do you mean by data recognized as duplicates ? Are you doing an ofximport or csvimport shippped with pynYNAB ?

@chbndrhnns
Copy link
Author

I am using the methods from https://github.com/scottrobertson/fintech-to-ynab/blob/master/python/ynab_client.py.

So the recognition as duplicates is not done by pynYNAB but by fintech-to-ynab, sorry for the wrong scope here.

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

No branches or pull requests

2 participants