God this upgrade is becoming a pain in the arse.
Got another issue with accessing Corrective Actions from the DMR ellipsis, i am getting the following error
I can access CA fine from the Menu and the custom layer works fine, what have i done wrong, it worked fine before we upgraded.
If i remove the custom layer from CA it opens fine from DMR…
This system is borked!
New menu security is fun.
Two options:
1:Custom Layer on DMR, change the app-open to launch your customized menu item, put the custom layer for DMR on the menu. (if you want DMR to use your custom Corrective Actions layer, you will need to go this route)
2:Add the Base menu into processes (so that it doesnt show up on the main menu) - then DMR will be able to load the base.
Are you multi-company and do you have a custom layer on that item?
We are not multi-company in a sense that we only have one production company, there is another setup but is not used. We have a custom layer on Corrective Actions but not DMR
Not sure where the app-open is but i have found this which i have added the layer to -
Will see if that works.
I believe you actually want to remove the layer and repoint the app to the menu id, not that full string.
So put the menu id in the View section?
If what you currently have does not work, yes. I have that in my list of things I have to change during our upgrade to 2025.2, the way you have it works prior to 2025.2 but after that I have had to remove the layer reference from the launcher and point to a specific menu id that contains the layer.
Unfortunately trying to do it before 2025.2 doesn’t work, at least not in 2024.1.
Do you think that i have selected the right event?
TBH, I do not know, I would assume so but I’ve not customized this screen so I have not done this specific thing.
I would say your start item probably needs to be an Event>Override and then select the original Event you want to override (the one you copied to create this).
I believe so, yes, this has been my experience with 2025.2 (the override has always been that way).
This works, i find it rather backwards that we are having to do this whereas before, prior to 2025, it wasnt an issue.
We just ran into this issue today as we upgraded to 2025.2.10 over the weekend and this wasn’t uncovered during our testing. I agree that this is “rather backwards”. To me it is an excuse for something Epicor broke!! We did not have a custom layer on DMR Processing but did on Corrective Action. Now I have to create a custom layer on DMR Processing to override a standard Control in order to use my custom layer in Corrective Action. Very frustrating!!!
