Deduping UI actions can break when there are two UI actions with the same action name and the same specificityDescription‘Same specificity’ refers to the same table and view combination. If two UI Actions have the same action name and are configured for the same specificity, they cause issues with deduping. This becomes apparent when they are overriding the same parent UI action, and the behavior can be different depending on what database is used.Steps to Reproduce This was discovered in CSTASK1349762 where two different instances had the same actions but the database was returning them in a different order so the deduping worked incorrectly and the wrong ui action was visible.WorkaroundEnsure that UI Actions for the same table/view combination do not have the same action name (ensure unique action names).Related Problem: PRB2006248