How have most of my Payees become Hidden? (Q Mac)

Options
newcastlelinda
newcastlelinda Quicken Mac Subscription Member ✭✭✭

I was just looking for a few transactions by a certain payee and decided to merge all the variations of the Payee into one.

When I went to the Payee window do find them all and Merge, I discovered that some versions were Hidden! I don't recall ever Hiding those Payees. I looked further and now have discovered that a majority of my Payees are Hidden … ~5000 out of ~8000 (I've been using Quicken for over 30 years).

What's up and how do I fix this other than One at a Time!?!

Quicken Mac Subscription - iMac - Quicken Mac user since 1994
Tagged:

Answers

  • Jon
    Jon Quicken Mac Subscription SuperUser, Mac Beta Beta

    I don't think there's any way to toggle the Hidden flag on groups of payees, it's one at a time. You can sort the Payees list by the Hidden column to group them all together which might speed things up a tiny bit.

    I don't recall there being anything that would automatically hide Payees. Looking over some of the hidden Payees in my list I don't see anything that doesn't look like I would have marked it Hidden myself.

  • newcastlelinda
    newcastlelinda Quicken Mac Subscription Member ✭✭✭

    I also thought that sorting by Hidden would help but it actually is slower. If you sort your Payees by Hidden and then uncheck one, that Payee is moved to the unhidden partition of the list and you have lost your place!

    Thanks for the idea though.

    Quicken Mac Subscription - iMac - Quicken Mac user since 1994
  • UKR
    UKR Quicken Windows Subscription SuperUser ✭✭✭✭✭

    Have you considered merging payees instead?
    This might be faster than trying to unhide a gazillion entries one by one. And it cleans up your Payee List in the process, reducing its size. For example, merge all variations containing "Starbucks" to a single payee named "Starbucks".

    See Managing payees (quicken.com)

    Do create a backup of your Quicken data file BEFORE you get started working on this, just in case …

This discussion has been closed.