IrizA, I do have to give you credit for actually reading my reply and addressing it directly. Most of the time I just see a previously posted "solution" posted verbatim again as if done by bots. I have not found contacting QuickBooks to be at all useful. I usually have to find the solutions on my own. It would be nice if Intuit were truly concerned with their customer's experience, but I have not found this to be so. Contacting customer service usually results in more time (hours in my experience) and trouble than it is worth. And it is not so strange that QB is reverting back to Flat View. If you simply google it (see screenshot of the first 4 items that pop up going back to 2020) there are a number of pages that pop up with solutions to try. For that matter you may look it up with in the QB support community and you will find others that experience this as well. Never once has customer support helped me fix an issue with QB. I have always found the solution either for myself or by some article written by nice people who share their knowledge on how they fixed the problem with others online.
I have found that community support just offers rote answers (most likely bots), without digging into the real issues that people need help with. It doesn't do any good to submit tickets or offer suggestions to QB. I have yet to meet a developer that believes the issue is with the software that they develop. The go-to is always to blame the user and to just shrug most everything off as the ignorance of the customer. Nothing is ever done until they hear from the masses, then, and only then, do they look into their programming, find the bug then fix it. That is if they feel like it. I guess when you are a company as big as Intuit you no longer really need to care about the end user experience.
I'm a disgruntled Intuit user, trapped by integration with everything under the sun. If it wasn't for the integration that allows for automation and web connection, I would go back to Sage in a heartbeat.
How about someone say "Hey, this sounds like a real issue. I'll save you time and forward this on to development"? After all, we aren't using QB for funsies, we've got real work to do.
