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?
1 Like
I’ll start it off with a simple one
Show actual user who approved a Time or Expense entry using someone else’s workforce
5 Likes
Seriously improve Kinetic grid component performance
Not mine, but I experienced this today 
Nevermind it is closed.
Document how the quote fields in Demand Entry work.
Using the QuoteNum & QuoteLine fields in Demand Detail allow you to accept EDI Demand and link the resulting Sales Order to a Quote. This is awesome functionality, but it’s not documented in the EDI Technical Reference Guide, nor in the System Help.
Allow Cloud Users to be early adopters of first release of a new version
Epicor is looking for volunteers to test new releases - why not allow Cloud users to have Pilot upgraded early?
When Epicor is prepared to enable Beta instances, it would be beneficial to allow Cloud users to upgrade their Pilot environments to the latest release. This approach would create a win-win scenario by increasing the number of users testing the newest version while also providing valuable insights into the impact of changes on Pilot databases.
Who said Cloud wasn’t allowed?
We are allowed to - just have to sign up for controlled release and commit to testing the new features.
2 Likes
@Banderson @aosemwengie1
The idea is, if 2025.1.1 is okay to do a controlled release, why not make it optional for any cloud customer? Why should they have to wait until 2025.1.3?
This idea came from a response I received from @timshuwy to my suggestions of
For cloud users – offer that they could get 2025.1 now in pilot so they have a longer window to test it versus requesting to delay their upgrade. This approach everyone wins.
Tim responded -
"On prem customers do not get a copy of 2025.1 until GA unless they are part of the CR program, but cloud gets access once we get to the .3 version if memory serves me correctly. "
Not all customers are on EpiUsers group so they may not know that they could request to be in the CR program.
So its more stable.
1 Like
IIRC, CR releases in cloud were in a separate instance from Pilot or Prod. I believe the .3 referred to the patch and not the release. 2025.1.3 for example. The CR program is the one that gets the product to the third patch. Unless I’m misremembering…
Your right - it is 25.1.3 that is released a few weeks ahead of GA. Getting 25.1.1 a couple months prior to GA would better for some organizations to have to review in the Pilot environment.
1 Like
Surprised this idea has so few votes - for a business with multi level BOMs this is very problematic.
Prevent the Job Entry Assemblies tree view from | Epicor Ideas Portal