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
To get us started, I was moved by a necropost from @Hally:
Came across a new table for me…ice.PatchFld… What is this? - Epicor ERP 10 - Epicor User Help Forum
which spurred this Idea:
Remove Ice.PatchFld and replace with User Defined columns - KIN-I-5669
Ice.PatchFld has been allegedly on the way out for quite some time.
As a modest proposal, can we use the User Defined Column capability to add “new” fields to the
_UD table? Unlike customer added fields, these Epicor created fields would NOT have the trailing “_c” on the field names. For example, in 2024.1 there is a CRMMenu Field name for the MENU table. In this case, add CRMMenu to MENU_UD (without the _c). At the next upgrade, the field would be moved from the _UD table to the main table.
3 Likes
This needs more traction: Silently Pass Parameters to BAQs in App - 3679
Need to be able to silently pass parameters to BAQs from App Studio.
9 Likes
Can we get more votes for this? Make it easy to switch companies, PLEASE Enable in Context Company Switch in the Browser | 5607
This would be a huge selling point in moving to the browser, if implemented.
As we come to rely more on the edge agent this is going to become a bigger pain point. We need to be able to simultaneously test the new version of the edge agent with the new release without uninstalling the current production version. Support Running Multiple Versions of Edge Agent | 5662
6 Likes
I’m missing something… I think you can, right?
I mean, it’s not as fluid as a BAQ without parameters (basically slap the BAQ ID in the provider model and call it a day), but it’s doable with an event to populate the data view, right?
To prevent the slider panel from popping up, just do not populate the BAQ ID in the provider model.
I think @ridgea has tackled this…
But it should be as easy as it was in classic, and it definitely is not.
2 Likes
Wooo hooo I got a mention… Did I mention pressing enter in SO entry does not update the order totals 
!
3 Likes
This came up the other day:
Putting the BAQ ID in the Provider Model is a core method of populating a grid without dealing with extra events.
Just like the Where List, you need to be able to provide parameters there as well.
In addition, if you have a BAQ Search that uses a parameter (for whatever reason), you are not able to specify one there either.
The only place you can is in the erp-baq widget which simply is not enough.
4 Likes
This is a pretty “Epicor Support” thing to say…
9 Likes
Gotcha. I voted for it.
1 Like
Why would it? that seems a bit random. Do you mean using Enter as Tab?
How many people would support an Idea to have one upcoming release cycle with no new features at all, and all development focused purely on bug fixes/parity with classic?
- Yes
- No
0
voters
1 Like
They really need to fix many…many bugs with baq/bpm/function designers 
2 Likes
Voted No because it would a wasted effort. Guaranteed this will never happen. New features make money due to prospective clients. Epicor doesn’t care about classic anymore.
It’s highly likely they have different teams working on bug fixes/legacy vs the teams making new features anyways.
4 Likes
I mean, I agree, but how else to get the point across that there has not been enough focus on fixing the bugs and we are how many years into this kinetic journey?
5 Likes
OK, I get the idea and even love the sentiment a lot. But I would propose it slightly differently:
How many people would support continuous release of bug fixes and features like other cloud companies do (AWS, Microsoft, etc.)? New features would be turned on and off via Feature Flags and not big upgrade weekends.
- Yes
- No
0
voters
2 Likes
In light of the last several release cycles (multiple major delays, last minute rescheduling) up through the update we just had this week where the maintenance window was extended AFTER the update was already announced completed AND a second maintenance window was announced with almost no warning at all, its a no brainer that the current model is a total failure and must be rethought. I live in fear of what awaits me on Sunday lol.
8 Likes
Id even be in favor of slower major release cadence to prioritize bug fixes. I mean just look how many hotfixes we have for 2024.1.
3 Likes
My boss asked me recently, “What is the last stable release of Kinetic?”
I hope I didn’t laugh, but I probably did.
He knows VERY well the struggles we’ve had. It’s not asked in ignorance at all.
But my point is this - that there is no difference between “we fixed the bugs” and “we broke other things.”
4 Likes