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 Have two tables 'parent' and 'child'. On the 'parent' table, create a UI Action with action name 'action_name' and select the form_action checkbox. In the 'child' table, create 2 UI Actions with the action name 'action_name' and select the form_action checkbox. (you can optionally test these out with different orders to see different behaviors). When visiting a form for the 'child' table, you will see one of three situations: The correct action is shown (it worked by sheer luck of the order processed). The wrong action is shown (e.g. either the parent, or the wrong child action is being shown). No actions are shown.WorkaroundEnsure that UI Actions for the same table/view combination do not have the same action name (ensure unique action names).Related Problem: PRB2006248