Weird question, but am sure there is someone with the same quirk.
In our 10.2 environment, I had some code to enable the editing of job comments while the job was released and engineered. Mainly because once it is on the shop floor, we don’t want the cust service team to keep unengineering/re engineering it all the time when they update any of the job comments (and other comment fields we have created).
Is there a similar way we can allow these job entry fields to be updated inside job entry via editing the app layer?
We have always been (and still are) able to update job comments on Open jobs without unreleasing/unengineering in Classic Job Entry. However, on Kinetic Job Entry we cannot. I don’t see where we have any customization on the Job Comments that allows update in Classic so I am thinking it was standard unless i am not looking in the right place. I have checked for data directives, method directives, customizations on the field.
Does anyone know if this was standard in Classic? This was just brought to my attention as our users are finally starting to test Kinetic Job Entry.
Good to know, thanks for taking the time to submit a case. We were going to upgrade to 2024.2.12, so may just look at 13 now or hold off for 2025.1.
Interestingly, when I looked at all the data rules for those fields, they were all locked with no way of adding/removing anything to them.
We do have an updatable dashboard for production to update Job header UD comments, I may see if I can link it to a button in Job entry/tracker for our customer service and materials teams to update comments on a slide out.
Update: This was not fixed in 2024.2.13 nor was it in 2025.1.5. I had to open a 2nd case and have support open a problem. Epicor development is now saying it is fixed in 2025.2…
