Validation errors too vague to act on

System · October 17

This discussion was created from comments split from:

.

Eric in North Texas · October 15

I have similar problems, though have yet to experience the 'unable to report' error. When I validate a file I receive error messages that I cannot act on because they are too vague (e.g., a problem with a corrupted account with a description of the account using, what we called in the old days, 'machine code'). Is there a way that we, as users, can raise the profile of this issue with Quicken? TBH, I have been much happier with Quicken since they forced us all to the subscription model. I was skeptical, but they seemed to have focused very well on their efforts on other problems that users had. This one has been going on for maybe 30 years.

Quicken Kristina · October 17

Hello @Eric in North Texas,

Thank you for reaching out! The way to bring this to the attention of our product and development teams is through Idea posts. Ideas that receive enough votes may be implemented in the future.

There are a couple existing Idea posts asking for improvements to the Validate & Repair function. If you'd like to see these implemented in the future, please add your vote and a comment:

https://community.quicken.com/discussion/7955209/validate-report-to-display-transactions-at-issue

https://community.quicken.com/discussion/7880500/validation-should-specify-what-it-changed-32-merged-votes

If neither of these covers what you'd like to see improved, then please create a new Idea post. For information on doing that, please see the post linked below:

https://community.quicken.com/discussion/7849425/creating-and-voting-for-ideas-in-the-community

I hope this helps!

Validation errors too vague to act on

Comments

Categories