Inputting transactions...Invalid Category!! Why?

[gusgf]

Why am I being forced to input a category?

Where in the documentation does it say this is not an option?

Please tell me this is not necessary.

[GabrieleV]

Category is mandatory. If you don't want it, simply use a fake one..

Inviato dal mio Nexus 5

[gusgf]

Category is mandatory. If you don't want it, simply use a fake one..

Inviato dal mio Nexus 5

Seriously. So why on the Android version it is not required?

Would be nice not to have to assign a category but it's no big deal.

[luigi3]

Hi GabrieleV,
why also Payee is mandatory when I insert a transaction from windows app? From android app is not mandatory.
Thanks

[gusgf]

Anyone care to comment on the discrepancy between the Android and Windows apps.

I assume it's down to coding and can be changed. Can this be done on the next version please?

Functionally there is no sense to it. 

Otherwise it's a fine app

[GabrieleV]

I don't know Android version, I think that they will insert a dummy or empty one. Try to open a DB created on Android on Windows and show what happens with categories and payee.

Inviato dal mio Nexus 5

[gusgf]

I don't know Android version, I think that they will insert a dummy or empty one. Try to open a DB created on Android on Windows and show what happens with categories and payee.

Inviato dal mio Nexus 5

That's what I've already done! 

[GabrieleV]

And so what happens?

Inviato dal mio Nexus 5

[luigi3]

And so what happens?

Inviato dal mio Nexus 5

For payee, in the android db, when it is put into windows app, the field is "error payee". If I add a transaction on windows app, the payee is mandatory, but on android app no.

[GabrieleV]

Ok, so use the same error payee for your transaction on Windows..

Agree that should be better to allow user if enable/disable payee, but it isn't really difficult to always choose "error payee"

Inviato dal mio Nexus 5