Thank you.
I want to add about 20 emoji to this. but, in short:
Here comes the 
bait…
So, the description is wrong, is an easy fix, makes Epicor look bad. It leads people astray. (No offense @nmulkey – you actually saw through the lies.) Sure, all true.
But what I think this really emphasizes is how Very, v e r y hard it is to communicate problems to support/development.
Problems.
It’s hard to communicate problems to them.
Not “why did MRP do this?” Not “Please remove this landing page.” Problems are a mystery to the crew.
No updates on the PRB for seven years, except that random mass update we all got for some odd reason. I ask about the PRB, tech says it is fixed, yet the PRB was never updated.
Then over the weekend I get an email saying the PRB was “updated with comments.” The comment isn’t in the email, nor in anything I can see in the PRB. Status is still Not Yet Planned. But it does imply that someone (probably the tech) read the PRB - the relevant one. Yet the response to me is to say that it’s fixed when it is not.
The point is, this is what we do see, and what I can illustrate, but it’s really just a microcosm of how you are truly talking to a wall when talking to Support. It gives you no confidence in the communication.
AI will fix everything, right?
