We’ve two customizations with the same names after we upgraded our systems. One is passed while the other is in the status of warning after verification. Anyone knows how this can happen and how to handle this? Should we delete the one with status of Warning? Can we disable the one with the status of warning and how? Thank you for your time.
Hi Ben,
We have had this happen when one customization has been saved with a company assignment and another customization (same name) for “All Companies”. (we are not multi-company). See first screenshot associated field.
I would review what you have in Menu maintenance for whether you have All companies checked or not per second screenshot and if one way vs other, compare to the customizations and ditch the one that doesn’t agree with your menu maintnance assignment. This is assuming that the customizations are actually the same… (i.e., otherwise I’d review the code/customization done to each and ditch the older one).
Nancy
Thank you Nancy!
Hi Nancy,
Our case is that the customizations and the menu item are all for all company.
Hi Ben,
You can also have customizations with same name BUT for different “Form Name”. See my screenshot customization maintenance above… I have customizations called Sales Order Entry TUSA on both Form Name = SalesOrderForm and Form Name = CopyOrderForm. This was done to get the customization to load properly automatically, but that’s another story. Do you have multiple SAME NAME customizations for SAME Company and SAME Form Name?
Maybe show a screenshot of your concerning customizations pulled up in customization maintenance?
Nancy
Hi Nancy,
Yes, I have two same name customization for same (all) company and same form Name (Order Entry).
Hi Ben,
huh. That’s surprising. Soooo if you want to try and ditch the bad one, maybe use Actions / Export on the bad one in customization maintenance, to make a backup copy. Then delete it in customization maintenance. Exit Epicor and come back in and see if the one you’ve saved in there works ok.
Nancy
Hi Nancy,
It is an Epicor upgrade bug. we need to apply “Enforce Validation (No Check)” option

