Investment Account Overview - historical performance - industry/category averages missing

scott62556

This issue was discussed in October 2018 but never resolved.  It is still an issue in Quicken Premier
2019 R18.16


.

mshiggins

Was there a specific discussion in October 2018 where this issue was discussed? It might help to start by reviewing that discussion. 

scott62556

yes I reviewed that discussion but I did not find a solution  Did I miss something?

NotACPA

How about providing a link to that discussion ... so we can review it also?

mshiggins

Here is the link to the prior discussion:

https://community.quicken.com/discussion/7792637/investment-account-overview-historical-performance-industry-category-averages-missing

scott62556

I reviewed this again and have the same conclusion.  Quicken (Sarah) indicated it would be fixed in April 2018 but there is no indication was resolved.  The discussion is now closed.  

NotACPA

"Quicken (Sarah) indicated it would be fixed in April 2018"   WHERE does she indicate that .... because it's certainly not in the thread that mshiggins provided the link for.

scott62556

Follow the link in the 1st paragraphhttps://community.quicken.com/discussion/7720164/portfolio-view-group-by-industry-has-no-industry-types-listed-anymore-only-unknown-and-cash

NotACPA

AHHH, so you actually mean that Sarah INDICATED in April 2018 that it would be fixed ... rather than it would be fixed IN April 2018 .. but she never said WHEN it would be fixed, as that's up to Development.

scott62556

Ok its now April 2019 and no change what can we do to get help.

Quicken Harold

Hello scott62556. 

Needing help?

You can reach out to Quicken Support at http://www.quicken.com/contact-support and one of our technicians to look into this and work towards a resolution.

We apologize for the inconvenience.

Respectfully.
~ Quicken Harold.

q_lurker

scott62556 said:

I reviewed this again and have the same conclusion.  Quicken (Sarah) indicated it would be fixed in April 2018 but there is no indication was resolved.  The discussion is now closed.  

Actually in April 2018, Sarah only said she had opened a ticket with Development.  I did not see any statement suggesting Development had identified the problem or agreed to fix that problem.