Issues with Portfolio Rebalancing with custom asset classes

Question

With reference to closed post:

https://community.quicken.com/discussion/7959543/issues-with-portfolio-rebalancing-with-custom-asset-classes

@Quicken Kristina I just received the R61.23 update and I see that the rebalancing table now includes custom asset classes - that's great… a very welcome bug fix. However, I see that the issue with using the colour BLACK for all/every one of the custom asset classes persists. This renders the legend and graphs useless when you have more than one custom asset class. I hope a fix for the legend colour coding is in progress.

Quicken Kristina · Answer

Hello @Arctic Hare ,

Thank you for letting us know this issue still is not fixed!  I can see the CTP for the issue is still open.  I let the team know that the latest update did not correct the issue, and included the screenshots you provided.

Thank you!

(CTP-12048)

Chris_QPW · Answer

Thanks for the screenshots and the explanation. I see what you mean now about the coloring.

It is nice to see that Canadian version is getting a new update, it would have been nice if that information was posted on this forum.

Arctic Hare · Answer

@Chris_QPW  @Quicken Kristina

First of all, and most important, I gave praise too soon. The reallocation table has NOT been fixed. The release notes indicate it has been fixed, but it has NOT been fixed. Still the same problem.

Screenshot of Version:

Screen shot of Portfolio Rebalancer (with personal information removed):

To be clear, this is taken from "Rebalance portfolio" button on the Investing Tab → Allocations view

*** NOTE that multiple asset categories are coloured a common black AND all the BLACK coloured asset categories are still missing from the Rebalancing table. And, you can't see this because I've removed the personal information, but the rebalancing numbers for what is included in the table are all grossly wrong because the calculation ignores the custom asset classes. No improvement has been made even though the release notes say it was fixed. These problems continue to render this important functionality as utterly and completely useless.