On Friday, it’s EpiUsers Frideas Day! Have you been to the Epicor Ideas Portal recently? If so, are there some ideas you want to encourage other users to vote for? Maybe want to add comments to an existing idea?
Keep the dumpsterfires to a minimum 
→ @klincecum 
Allow linking multiple job suggestions to one job in Job Manager
Allow creating one job for the same part with multiple demand links from Planning Workbench
I would love to get some traction on any of my ideas related to Collaborate. We are really trying to make a go of it, but they need to do some basic things to make it more useful to all of us - right now it is marginally useful at best; implementing some of the ideas there would greatly increase the usability.
I have sat in on the last Collaborate Epicor Advisory Update and voiced many of my opinions there - they seemed to be received well, but the entire presentation from their side was of little substance IMHO.
You can find my ideas and more directly at the Ideas Portal here:
https://epicor.ideas.aha.io/ideas?project=COLLAB
Thanks in advance!
Since @MikeGross is looking votes on a comprehensive request… I’ll put in my plea for votes:
https://epicor.ideas.aha.io/ideas/KIN-I-5507
Add a system wide inactive flag for all those codes you can’t delete but don’t want anyone to use. I see they should have it for Part Class in 2024.1, but what about Product Group, Reason Code, etc.
How many people are using zDoNotUse or zOBS in your description as a workaround 
Jenn
@Randy - how about we just get them to convert those Crystal Reports to SSRS for consistency? I’m voting regardless!
Thanks for the vote! The idea is agnostic as far as SSRS or Crystal goes but I’d vote for converting QS to SSRS.
I heard that they will be releasing some type of portal for public cloud customers to recycle the app pools, do a regen, without needing to put in a ticket with support. Could it be true? I want.
Yes Jeff they are working to allow us SaaS customers a way to do some functions from the Admin Console. It’s coming just not sure when.
It’s been promised for YEARS now. Most recently at insights they promised “this summer”. Pretty sure summer is over and still not a peep.
Voted on about 6 of them - we too are going to try this when we upgrade to 2024 so anything useful to us I voted on.
Be happy to join in on the PAB too, if they need folks.
Sometimes you gotta go get them votes!!
Voted & commented on yours just now - good idea.
KUDOS!!! Our larger group effort to improve email communications got moved to Gauging Interest and now has 36 votes - let’s show them it matters by giving it a few more votes
Comprehensive request to re-engineer all of the | Epicor Ideas Portal (aha.io)
And a few others
Delivered Pricing - Allow for the option to include freight in the Selling Price
ECM - Allow documents with Stamps or Annotations to retain stamps and annotations
ECM - Sort the Fields grid in Datalink and Integrations
Last one for today… I would be interested in seeing if anyone else is in this situation. If you don’t have QuickShip, you can’t use Phantom Packs if you want to Stage the packs. You can ship, but not stage. I put in an idea that both should be allowed:
KIN-I-5428 Allow stage with phantom pack
Looks like a younger me in the backgroup…
While we would love to fix the “Inactive flag” for all tables at once, this idea is TOO BIG and not specific enough for us to accomplish. this is equivalent to “fix everything”… this type of idea is not able to be prioritized.
We have a bunch of different smaller ideas related to an inactive flag, and we have been knocking them off one by one as the user base prioritizes them.
Example:
While I agree that’s it’s too big to implement at once, PLEASE start with a holistic plan of how to do it so it’s consistently applied everywhere!
Huh, when did that change occur? Back around 2016 I worked for a company that did not have QuickShip (AKA “Manifest” back then) and we phantom packed all the time. That was Epicor 10.0 and 10.1 days so maybe it’s changed but I’d be shocked Epicor would remove functionality.
so reposting.