1. Home
  2. Quicken Personal Finance
  3. Bug in QD2010 Spending report when deselecting tags?

Bug in QD2010 Spending report when deselecting tags?

Hi all:

Today I was looking at a YTD report for a selected category, sorted by tags. For this particular category all transactions are earmarked with 2 tags. I then went into "Customize > Tags" and deselected, one at a time, various tags, flipping back to the report with each deselection. I found, in the main, that deselecting a tag did *not* necessarily eliminate transactions with this tag from the report. The process was somewhat inconsistent in that sometimes the deselection of the tag *would* affect the report, and sometimes it wouldn't.

Going the other way, that is clearing all tags (resulting in a blank report) and then selecting tags one at a time, worked as I'd expect it to; with each new selection transactions with that tag showed up.

I'm positive that I've used this deselection process in the past when looking at this particular category and that the report worked as expected, i.e., any deselected tag would disappear from the report. Seems like some update to QD2010 affected things.

Can anybody else confirm?

TIA

Tom Young

Reply to
TomYoung
Loading thread data ...

"TomYoung" wrote in

I tried to test this, but I'm not confident I know exactly what you did and exactly what you expected to happen.

I tested in Q2010 RPM R10 (and Q2008 Premier R9).

To make it easier to examine the problem, I created 4 test transactions, in a checking account:

1.) Category=Test Cat; Tag=Tag1 2.) Category=Test Cat; Tag=Tag2 3.) Category=Test Cat; Tag=Tag1:Tag2 4.) Category=Test Cat; Tag=Tag2:Tag1

I don't know what report you used; I used Banking > Transactions.

In the Customize dialog, on the Tags tab, I selected Tag1 and Tag2. The resulting report listed all 4 transactions.

Then I changed the Customizations to exclude Tag2 (leaving Tag1 selected). The resulting report listed: Transaction 1 (Tag=Tag1) Transaction 3 (Tag=Tag1:Tag2) Transaction 4 (Tag=Tag2:Tag1)

Excluding Tag1 (and leaving Tag2 selected) produced: Transaction 2 (Tag=Tag2) Transaction 3 (Tag=Tag1:Tag2) Transaction 4 (Tag=Tag2:Tag1)

I tried excluding all tags, creating an empty report, then adding the tags back one at a time ... same results.

My interpretation of the results I saw is that when there are two tags assigned to a transaction, excluding one of those tags does not override the inclusion of the other tag.

Reply to
John Pollard

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.