Over my head, but you had charts so I voted!
And welcome to the group!
2 Likes
Vote count DOES have an impact. Our dev team didnt used to acknowledge Idea votes (or “connected customers to enhancements” in our old processes), but now, when we are discussing new features, the vote count is nearly always an issue.
- If something is very easy (less than 10 hrs) but has some votes, it might be put in, simply because it is easy and makes sense.
- If something is very difficult, with 1000s of hours of dev/QA/Documentation time, + will need lots of education and field changes, it may get deferred.
Cases in point:
- @Mark_Wonsil’s devops idea has been discussed every 6 months, but has been deferred due to the complexity and the fact that we were not ready for it. This idea has many votes.
- BAQ as a source for another BAQ… this one also sat around for a while, even with its 366 votes. It was expensive, and it also required changes to the BAQ screens, and we didnt want to do that until BAQ was editable in the browser… so it waited until we were ready to put it in.
- Most recent update has a “very inexpensive” feature that only had a couple of votes when we decided to do it… that feature was to display the SUPPLIER NAME at the top of the Supplier Entry/Tracker screen when in the activity cards. This new “feature” is an obvious win, QA impact is very small, documentation impact is very small, and it should not affect any of your customizations in the field. This is a win/win/win in all areas.
Our Process for each new release is to look at ALL the heavily voted items, and have them “sized”… then they get ranked for importance and impact… then we put them into the plan. currently, anything above about 25 votes is “sized”. BUT as I said before, even things that have one vote are considered if it is “obvious” that it is very small and should be done.
10 Likes
I didn’t mean to imply things were selected via a random number generator. You mention a lot of factors besides vote count that go into deciding what gets done, and those factors aren’t transparent to us. So its easy to get discouraged.
It would be cool if the ‘sizes’ were published on the ideas, and that there were updates communicated on the top 10-15 ideas by votes even if they are not coming in the next update. Marks idea might have been discussed every 6 months, but all we were hearing was the ringing in our ears.
Thank you for participating and communicating. I know you are trying, even if some of us are not easy to please.
4 Likes
May I suggest a starting place?
Provide a text-based representation (XML or JSON) of each customizable object
Kinetic UI? 
Done.
SSRS? Done.
Kinetic Functions Done with save as JSON.
.DOTNET Screen Customizations? Why bother?
and be able to import and export objects in that format.
Remember, the Idea isn’t to implement DevOps, it’s to make it easier for the users to do so. We’re, well, I’m looking for the hooks.
Thanks!
BTW, not saying this is easy. Serialization/Deserialization with versions can be a real PITA.
7 Likes
Functions can be exported in json format, just select the file type.
But insides it will contain parts of code, not the complete function source code.
Also they will be just downloaded in the standard folder in browser, unless you have Save as for downloads.
BAQ export also is bunch of xmls inside zip file 
2 Likes
It would be amazing if some of this can be summarized back to us, either in a post here or on the individual ideas that were reviewed. Right now we see if it changes to “in development” but not anything else.
6 Likes
This one is really driving me crazy lately:
Bring back record selectors for record nagivation
3 Likes
Now we are getting AI responses to our ideas? Did Prism write this?
https://epicor.ideas.aha.io/ideas/KIN-I-6022
10 Likes
I’m guessing Musk’s Grok as it’s a bit snarky, at least the second response.
Arturo is agreeing with the spirit of the idea after all. We asked for stability and that’s the word that I’m looking for. Some folks are going to have to sit at 2025.2 for a bit, so they don’t want to go back and maintain it if possible.
4 Likes
Cloud customers do not have the option to sit at 2025.2 for a bit. Kinetic must be functional. Here is my idea, but you can’t vote for it.
https://epicor.ideas.aha.io/ideas/KIN-I-6377
1 Like
Speaking of cloud customers, it would be great if we could actually have the latest releases, as is the promise of cloud:
https://epicor.ideas.aha.io/ideas/CMP-I-13
2 Likes
No prism did not write this, While I confess that I used AI to clean up my paragraphs, the words were all mine, and I personally typed this in. Aha does not have an automated AI engine to fill in responses.
ALSO, One of the reasons we have said that we will not be doing this is because we have also received requests for some really great ideas (that many of you voted for) that we want deliver. If we were to proceed with “the boring edition” the few cool new feature we are delivering would not be there. (see the list here: Log In - Epicor Identity)
We have previously received criticism for claiming to have provided something that others considered was only half delivered. In the case of this particular “boring” proposal, there is no such thing as partial delivery… it had a specific version and a specification, and we elected not to continue with it in favor of focusing on quality WHILE CONTINUING to add new features. At that point, I had a choice: close it or keep it open and ignore it. I decided to be informative and close it and tell you why.
In our efforts to collaborate with you all, we’re working internally to design a short survey to gather your input. We’re planning to share it with EUG for circulation as well as posting it here on EpiUsers within the next few days.
6 Likes
I do dislike highly voted on ideas just sitting in limbo with no response. I appreciate your efforts in communicating with us customers. I too was disappointed the idea was dismissed, but was slightly encouraged by Arturo’s response, "BUT you have my commitment that this release will be more focused on quality and stability in preparation for 26.1 and our future together. " in that the sprit of the idea was taken to heart.
2 Likes
3 Likes
Thank you @timshuwy
I think we’ve beaten this horse to death. Closing this Frideas , a new one comes out tomorrow!
7 Likes