Choices [sys_choice] are skipped if they have same name/language/element/value but different dependent value in application updateDescriptionChoices [sys_choice] are skipped if they have the same name/language/element/value, but the different dependent value in an application update.Steps to Reproduce 1. Create a Scoped App, then create a table with a Choice field.2. Create some choices for the Choice field. The tricky bit here is that, make sure we create some duplicate choices with the same Labels, Values, Languages, and Sequences.3. Download the application package and install it in another instance.4. In the target instance, manually remove 2 - 3 duplicate choices, then delete the corresponding sys_update_xml entry or mark the entry with 'replace_on_upgrade=true'.5. Install the application again and the removed choices will not get installed.Ref. KB0657356 "Updating Choices in Scoped Applications" : When installing applications, updates for Choices are handled at the sys_choice level, not sys_choice_set. So for duplicate choices, the installation believes they are installed already and therefore doesn't install them again (or the installation does an Update to the choice record with the same settings instead of creating a new one).WorkaroundAfter carefully considering the risk of making the required change, we have decided not to put in the additional coalesce criteria on the 'dependent' value of choices entries. We apologize for any convenience caused by this limit. To work around this limit, one of the options is to differentiate the choices by giving them different values but keeping their labels the same.Related Problem: PRB1456150