Running 2025.1 in the Public Cloud. Have an interesting issue with one of my clients after the upgrade over the weekend.
We have two companies, pretty much do everything in CompanyA and make it “ALL COMPANY”, so CompanyB gets the same menus, screens, etc. On CompanyB, the Part Tracker button is now grayed out for EVERYONE in CompanyB. I am a system manager, I can clock in as an employee in CompanyA and Part Tracker works, but if I clock in as an employee in CompanyB - Part Tracker is disabled. Same goes with everyone in CompanyB.
We run an App Studio layer on the MES screen (we have some added buttons). Some things I’ve tried:
- If I have production started on a Job, I can scroll in the grid view that shows the active transaction, right click on the part, open with Part Tracker just fine.
- I added a button, added the same click event to open the Part Tracker Menu ID that’s on the canned button, and that works just fine.
- The canned button has an EpiBinding to MESControl.PartTracker. I removed that on the layer, still can’t use it.
- I added an EpiBinding to MESControl.PartTracker to the new button I added, that made that button disabled.
- I changed the EpiBinding on the new button to MESControl.JobTracker (just for giggles), the new button works just fine (assuming I have access to Job Tracker).
- I went into Handheld/MES Menu Security Maintenance and all the checkboxes appear to be set, including Part Tracker under the General area.
- I cleared any company specific menu security on Part Tracker and made the menu option it runs to be the canned. Still not enabled.
It appears there’s an issue with MESControl.PartTracker not getting set properly in just CompanyB?
Has anyone experienced this? Any body have any particular insight into the MESControl dataset and how it gets created?