Frideas for 26 July 2024

Kinetic ERP
1

OK… I got a one day head start, but since the Kinetic product team is currently going through our “grooming” process for Kinetic 2025.1, we are looking at some of the ideas that are out there that can be put into this next release.
THIS idea to Enhance MRP Urgent Planning is one near and dear to my heart since:

  1. I created it
  2. the date I created it was my last day as a consultant, just before I migrated into Product Management.
  3. I feel it could make a huge impact on many customers.

Read it… understand it… and if you agree with it… vote on it :wink:

2

That link still goes to the old aha site FYI.

3

I’m going to make another plug for this one:

Improve error message handling for errors with Correlation IDs

Its frustrating not being able to look up the exact error (coming from on-prem).

4

Just saying… I really love Epicor Ideas…

5

The aha Ideas platform in general is pretty great. We may look at implementing it for our continuous improvement process internally.

6

I had not even thought of that but what a great idea… Pardon the pun

7

Thanks… i fixed it.

8

These two should should be pretty easy:

9

well…you would THINK that this would be easy (it WAS scheduled for 2024.2)… but it turns out that when we tried, the system performance went really bad. The reason is that in order to show the green checkmark, we have to do additional queries against each line and then change graphics, and this became a bad performance item, and we undid the change. We have not given up, but for now, we are not doing this.

10

There is already an idea that includes this:

https://epicor.ideas.aha.io/ideas/KIN-I-4813

11

I think the idea you refer to was related to automatically adding the data, as desitinct from tracking when the relationship was established. If you were importing suppliers from another system you may want to include that historical data.

12

Then these two should be merged as I linked to an existing idea @timshuwy . I did not create either one.

13

:astonished: Well in that case, is @Hally’s sub-idea of a tool tip a possibility?

14

Hi @timshuwy , could you elaborate why the extra queries are necessary? Why isn’t it as simple as updating the .svg file for a complete material?

image
image662×348 20.9 KB

image
image166×170 5.73 KB

15

I’m also super curious about this…

16

I may not have fully understood the problem nor explained it correctly… that said, I know that one of our best programmers was on this, and he built it but found that performance was not good. It is our goal to not negatively affect performance for something achievable in a different manner. Like i said, we have not given up… just deferred it.

17

@timshuwy Can I get your input on this? I’ve not experienced this one before. I assume it’s one of those ‘internal’ Ideas that it’s been merged with, and that’s why I cannot see it.

image
image1156×398 46.6 KB

Thanks!

18

I’ll plug a few of mine - these are big deals if you really use ECM for anything other than Kinetic attachment storage
Recycle Bin - allow us to redirect the restore | ECM
Allow documents with Stamps or Annotations to Retain them | ECM
APR Add Docstar Attachment widget needs a Versioning function | ECM

And one for Kinetic
Allow for the option to include freight in the quote line | Kinetic

19

If you love me, or if you love freedom.

free freedom GIF

Roll back Custom Code Restrictions that are no longer relevant with the move to AKS

FFS, it just gave me an error (warning) on object.GetType().Name :roll_eyes:

20

Predictive search is big game changer to be able to just type in a part and retrieve it based on “Contains” logic. I have a customer that has built their whole sales model around this capability.

I just got the rejection from development on predictive search today.

We have updated the functionality to align with the classic application as part of this ticket: https://epicor.atlassian.net/browse/ERPS-238143. As it is working as expected, we are rejecting this issue.

This is a big step backward for Epicor - the fix is just put it back in, as it is working fine in 2023.2

I have put in an idea to keep it.
Keep Predictive Search to utilize “Contains” vs “Start With” search as it is in 2023.2