nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

It looks like the cure created a new disease

Since_TheBeginning1

I see where Quicken posted they found the 'cure' for duplicate transactions and that the system would 'fix it' — this was posted 6/2. For me on 6/3 Quicken went in and wiped out a ton of non-duplicative transactions, thereby effectively blowing up my accounts (I note I did not have the duplicative problem in the first place). Sorry but the timing lines up too well for these two items not to be inter-related.

Find more posts tagged with

Comments

Chris_QPW

I'm curious, do you use Sync to Mobile/Web?

Since_TheBeginning1

Chris — No I do not.

After several hours across many accounts I found that entries that were made by me prior to the system downloading them were wiped off the account, while entires that were a result of downloading were retained. I'll stand by my contention the 'solution' to the multiple entry problem (which I didn't have) was too robust and wiped out directly entered transactions, seeing them incorrectly as duplicates. I challenge anyone from Quicken to prove that wrong.

NotACPA

A duplicate, in Q terminology, would have to have the identical FITID as a prior transaction … which a "directly" (i.e., manually) entered transaction can't possibly have because that's not a field that's accessible thru the keyboard.

Since_TheBeginning1

Any thoughts you might have as to what it was would be greatly appreciated.

jacobs

I found that entries that were made by me prior to the system downloading them were wiped off the account, while entires that were a result of downloading were retained.

Just for clarity, are you saying that a transaction you manually entered was downloaded, matched with the manual entry, and then the matched entry disappeared completely? That's a problem I haven't heard anyone report before.

Since_TheBeginning1

Yes that is exactly what happened

Boatnmaniac

Sometimes QWin users will report transactions "disappearing" from the register. Typically it is not that the transaction actually disappeared but rather that the account register was not sorted by date so it was not in the register where they were expecting to see it. Once they sorted the transaction by date they were able to see it in the register where they were expecting to see it. Does QMac have register sorting options and it that register sorted correctly?