Quicken 2017 R18.8 Build 26.1.18.8

Open Quicken 2017 Rental Property Manager version and it auto updated to the new build number. All seemed good until I downloaded transactions from my
credit union. Noticed that the two IRA accounts had missing transactions for Feb1 and March 1.
Downloaded the files in both QFX format and CSV to compare. Open the QFX with Notepad and compared to the Excel file and all transactions are in the downloaded files when compared to the online site transactions.
Both formats looked good, could not see any corruption. Reloaded the Quicken file from a backup and downloaded the files again - same missing entries for the same two dates. All other transactions show correctly.
All other accounts updated correctly and many had entries for the same dates so that sort of does away with a common date problem (I think).
The online accounts are correct and I compared entry for entry on the IRA accounts. Found that back in Jan, the credit union made mistakes in our IRA accounts and had to make "Reversals" on amounts withheld for RMD's and taxes and then reentered correct amounts and those entered correctly in Quicken.
All the transactions show correctly in the downloaded files but when they are imported to Quicken, those two entries for Feb 1 and Mar 1 for two IRA's do not get imported to Quicken.
I modified 1 QFX file so it had only the headers, two transactions that were missing and the footer info and imported that into Quicken. No error messages of any kind but again, those two transactions never showed up.
Sent files and note to Quicken Help but wondering if anyone else is having a problem with this update?
Bob S.
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
On 2019-03-05 04:20:27 +0000, n/a said:

If the missing transactions are in the QFX file, I suspect the reason Quicken did not display the transactions is because their FITIDs have previously been imported.
You could coerce their appearance by altering the FITIDs or by importing the QFX file into a temporary account.
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
"Sherlock" wrote in message

This corresponds to what you said from what I found on the Quicken site:
"FITIDs need to be unique for each transaction within the same account. Quicken filters out all transactions that contain duplicate FITIDs."
This would seem to be the problem so I dug into Quicken file (OFXLOG.txt) which is the same one that get sent when you send a report in. I then did a search and found both transactions in the OFXLOG file for the dates of 02/01 and 03/01. FITIDs are different, Reference numbers are different and everything else appeared to be normal with the entries.
But.... thinking you are correct because all the info needed for the transactions to be entered in Quicken is in the downloaded files from the credit union and I find corresponding entries in the Quicken log but the transactions are not recorded in the record for the account. So something must be filtering out those dates.
Haven't had the chance to do it yet but I have Quicken installed on another computer. I'm going to air-gap that puppy and then import the QFX files I downloaded (and saved) to see if the transactions show. That Quicken install has not been updated with the last build so I'm hoping it will continue to work when it finds it's not connected to the internet and can't update itself.
If that works and the files are imported and show correctly that pretty much points the finger at the latest build update Build 26.1.18.8.
I was going to try doing the import to a temporary account as you suggested but couldn't figure out how to do that and still retain the original account intact other than backing up, deleting the account, importing the QFX file and see what happens. Then restore from backup. If you have a better suggestion - fire away.
Thanks for your time and I think you nailed the reason (filtered FTIID's) - just need to find the cause now....;-)
--
Bob S.


Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
"n/a" wrote:

This corresponds to what you said from what I found on the Quicken site:
"FITIDs need to be unique for each transaction within the same account. Quicken filters out all transactions that contain duplicate FITIDs."
This would seem to be the problem so I dug into Quicken file (OFXLOG.txt) which is the same one that get sent when you send a report in. I then did a search and found both transactions in the OFXLOG file for the dates of 02/01 and 03/01. FITIDs are different, Reference numbers are different and everything else appeared to be normal with the entries.
But.... thinking you are correct because all the info needed for the transactions to be entered in Quicken is in the downloaded files from the credit union and I find corresponding entries in the Quicken log but the transactions are not recorded in the record for the account. So something must be filtering out those dates.
Haven't had the chance to do it yet but I have Quicken installed on another computer. I'm going to air-gap that puppy and then import the QFX files I downloaded (and saved) to see if the transactions show. That Quicken install has not been updated with the last build so I'm hoping it will continue to work when it finds it's not connected to the internet and can't update itself.
If that works and the files are imported and show correctly that pretty much points the finger at the latest build update Build 26.1.18.8.
I was going to try doing the import to a temporary account as you suggested but couldn't figure out how to do that and still retain the original account intact other than backing up, deleting the account, importing the QFX file and see what happens. Then restore from backup. If you have a better suggestion - fire away.
Thanks for your time and I think you nailed the reason (filtered FTIID's) - just need to find the cause now....;-) -----------------------------------------------------
I believe you did not fully grasp the meaning of Sherlock's comment when he told you that he suspected that the two missing transactions had the same FITID as transactions that had "previously been imported".
When a downloaded transaction is Accepted by Quicken, Quicken remembers the FITID of that transaction as long as that Quicken account exists in that Quicken file. Even if you delete a downloaded transaction, Quicken will remember that deleted transaction's FITID.
You can display the "Downloaded ID" column in your Quicken account and sort on it (click in its heading) to see if an existing transaction in the account has the same FITID as the FITID's in your recent QFX file.
But if there were downloaded transactions in your Quicken file that had the same FITID as your current Feb 1 and Mar 1 transactions, and those previously downloaded transactions were deleted from Quicken, you would not be able to determine whether your newly downloaded FITID's were duplicates by looking in the OFX Log or in your Quicken account.
The backdoor way to determine that (and to correct your problem) would be to follow Sherlock's suggestion to alter the newly downloaded FITID's (edit the file with Notepad and suffix something - almost anything readable - to the downloaded FITID), then try importing those transactions again. If they import, it's reasonably certain that they previously failed to import because they had FITID's that had been imported in some earlier download.
Or - and I don't understand why this was not the first choice, since there are only two transactions involved, and you're unlikely to determine the cause of the problem - you can just manually enter those two transactions into your Quicken account.
[I seriously doubt that you're seeing a problem caused by Quicken - new release, or not.]
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
On Wednesday, March 6, 2019 at 10:11:28 PM UTC-5, John Pollard wrote:

a

/01

g
er

I
't

uch

ed

unt

e
-

he

he

rt

he

ot

s

to

the

e

e

Actually unrelated to thread topic, intrigued by John Pollard's mention of clicking "in it's heading" to see the FITID. Could John explain a bit about WHERE (define "heading") I should click? I am on Q2019 Premier and have be en using Q since DOS days but always open to learn from John and other stal warts.
Thanks
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
"Al" wrote
Actually unrelated to thread topic, intrigued by John Pollard's mention of clicking "in it's heading" to see the FITID. Could John explain a bit about WHERE (define "heading") I should click? I am on Q2019 Premier and have been using Q since DOS days but always open to learn from John and other stalwarts. ---------------------------------------------------
Every column in a Quicken account "register" has a heading row. That heading row occupies one row just above all the transaction rows listed below it.
When you elect to include the "Downloaded ID" in a non-investment account register whose account is activated for downloading; the Downloaded ID will appear in its own register column, with a heading of "Posting Date". Click on the text in the Posting Date heading column and Quicken will sort the register on that column. [You can accomplish the same end by clicking the small gear-wheel icon in the register title row, hovering your cursor on "Sorting options" and choosing the sort-sequence you want (there are choices available there that there are not available in "heading columns").
[Note: you can not elect to see any "Downloaded ...." column in any account that is not activated for downloading. And you can never see any "Downloaded ...." column for any investment account (as of Q2019 R16.14)).]
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
On Thursday, March 7, 2019 at 10:07:03 PM UTC-5, John Pollard wrote:

THANK YOU!!! Don't know what we'd do without you.
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
On 3/7/2019 10:07 PM, John Pollard wrote:

John, did you mean to say that the "Downloaded ID will appear in its own register column, with a heading of "Posting Date"?"
Pete
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
"Pete" wrote:
John, did you mean to say that the "Downloaded ID will appear in its own register column, with a heading of "Posting Date"?" ---------------------------------------------------------------
Yes. As when I said:
"When you elect to include the 'Downloaded ID' in a non-investment account register whose account is activated for downloading; the Downloaded ID will appear in its own register column, with a heading of 'Posting Date'."
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
"John Pollard" wrote in message

John,
I certainly did understand about possibly having the same FITID's and I had checked sorting on the Downloaded ID column when Sherlock mentioned it. I also checked the Quicken files and did a duplicate check on those. After a lot of duplicate FITID checking and file modification, I then entered the missing transactions manually after making the post and not finding anything more on the Quicken site other than what I quoted.
And the idea of altering the downloaded file was also completed with no effect as I mentioned in my original posting - you missed reading that. Quicken in the past has had a bad habit of duplicating entries and causing a lot of manual work to sort that out so I minimized the downloaded file to only include the 2 entries when I re-imported it. No change, no errors.
While Sherlock was generous with his time to help assist with the details - my question to the group was simply:
"Sent files and note to Quicken Help but wondering if anyone else is having a problem with this update?
There are other problems being noted with this update if you do a search on this build.
As for it being a Quicken problem or not remains to be seen. I'm certainly no Quicken guru but I have worked with their software manager right after the transition from the former company to test some beta patches for this version (2017 Rental Property Manager). So yeah... Quicken has numerous problems.
I have not had a chance to test Quicken without the new build on my other system but when I do this weekend, I'll update my posts with any findings.
Thanks for your time,
--
Bob S.


Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
"n/a" wrote
John,
I certainly did understand about possibly having the same FITID's and I had checked sorting on the Downloaded ID column when Sherlock mentioned it. I also checked the Quicken files and did a duplicate check on those. After a lot of duplicate FITID checking and file modification, I then entered the missing transactions manually after making the post and not finding anything more on the Quicken site other than what I quoted.
And the idea of altering the downloaded file was also completed with no effect as I mentioned in my original posting - you missed reading that. Quicken in the past has had a bad habit of duplicating entries and causing a lot of manual work to sort that out so I minimized the downloaded file to only include the 2 entries when I re-imported it. No change, no errors.
While Sherlock was generous with his time to help assist with the details - my question to the group was simply:
"Sent files and note to Quicken Help but wondering if anyone else is having a problem with this update?
There are other problems being noted with this update if you do a search on this build.
As for it being a Quicken problem or not remains to be seen. I'm certainly no Quicken guru but I have worked with their software manager right after the transition from the former company to test some beta patches for this version (2017 Rental Property Manager). So yeah... Quicken has numerous problems. --------------------------------------------
Your response still does not convince me that you understood what I said.
Searching for FITID's that match the ones in a newly downloaded file, is NOT a conclusive way to determine that those FITID's have not been previously downloaded. If you find duplicates, that will be conclusive; but if you do not find duplicates, that does not prove there are no duplicate FITID's.
If the previously downloaded transactions that had FITID's equal to the FITID's in the newly downloaded file, have been deleted from your Quicken file, you will never see the duplicate FITID's in your Quicken file. Quicken retains (and uses) the FITID's of deleted transactions, but nothing you do will allow you to see them.
You say, "And the idea of altering the downloaded file was also completed with no effect as I mentioned in my original posting - you missed reading that".
I read your posts carefully before my previous reply and I've read them again now twice more, and I still do not see where you said you did what Sherlock and I suggested in that regard. The modification that I suggested (repeating Sherlock's suggestion) was "to alter the newly downloaded FITID's ...". I don't see where you said you did that. The idea was to guarantee that the two problem downloaded transactions would be guaranteed to have a unique FITID from any other transaction ever downloaded to that account in that file.
Something which I don't recall you posting is what "Connection Method" you're using. If you have a QFX file, that must have come from a Web Connect download. Do you always download from the credit union using Web Connect, or do you ever use another Connection Method, such as Express Web Connect? Or, was any other Connection Method besides Web Connect ever involved in your problem?
You may be able to get some indication about whether there is something other than duplicate FITID's involved by creating a New (test) Quicken file, and downloading/importing the problem account to that file. The results won't necessarily be conclusive, but they might help, especially if the "missing" transactions do not appear in the new test file.
As to Quicken having problems: that's hardly news. There is no such thing as bug-free software, and Quicken has always had some bugs. That changes nothing about the likelihood that your transactions are not appearing because of a bug in the your release of Quicken. It may be true, but it's not more likely just because your release, like every other release, has some problems.
The troubleshooting steps you've been asked to take, have at least a reasonable chance of helping to identify the problem ... unlike wild guesses (keeping in mind that correlation is not causation).
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
"John Pollard" wrote in message

John,
Thanks for your time but I really don't want this to be a controversial post which you are endeavoring to make it by telling me I didn't understand suggestions made or performed them to your liking. I certainly don't owe you any explanations and I don't appreciate your belittling comments.
So fuck off....
--
Bob S.


Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload
Right after making my post at around 11:53pm to John, I was closing down Quicken when a pop-up notice appeared from Quicken:
"A newer version of Quicken 2017 is available for download. Do you want to install it now?"
Hmmmm - maybe they fixed a problem or two....
Here's the Update Info for the new R19.1: ....................... Before you take this update we would recommend you to perform One Step Update to ensure that your data is synced to cloud and take a back up of your datafile. Quicken 2017 R19.1 Release Notes Fixed: A few internal bug fixes and improvements. .......................
Yeah - they had problems with R18.8
I'm updating to R19.1 and we'll see what happens.
Bob S.
Add pictures here
<% if( /^image/.test(type) ){ %>
<% } %>
<%-name%>
Add image file
Upload

BeanSmart.com is a site by and for consumers of financial services and advice. We are not affiliated with any of the banks, financial services or software manufacturers discussed here. All logos and trade names are the property of their respective owners.

Tax and financial advice you come across on this site is freely given by your peers and professionals on their own time and out of the kindness of their hearts. We can guarantee neither accuracy of such advice nor its applicability for your situation. Simply put, you are fully responsible for the results of using information from this site in real life situations.