Flow Designer tables extending var_dictionary do not coalesce on name and elementIssue Flow Designer Update set errorFAILED TRYING TO EXECUTE ON CONNECTION glide.28 (connpid=1854487): INSERT INTO sys_metadatajava.sql.BatchUpdateException: Duplicate entry 'var__m_sys_hub_action_output_9999999999a210108136231cd3961900-ta' for key 'name' java.sql.BatchUpdateException: Duplicate entry 'var__m_sys_hub_action_input_0999999999a210108136231cd3961900-ta' for key 'name'ReleaseMadrid and lowerCauseThere are several tables from Flow Designer which extend var_dictionary (which itself extends sys_dictionary) but do not have any coalesce strategy. Records on sys_dictionary coalesce on the same columns contained in the unique compound key, which are 'name' and 'element'. That means two records with different sys IDs are treated as the same record as long as the name and element values match.The Flow Designer tables do not follow the same rules, and coalesce on sys ID instead. That means, two records with the same name and element values will be treated as distinct records if the sys ID values are different. If you attempt to import a record like this via XML or update set, you will get unique key violation errors like this: java.sql.BatchUpdateException: Duplicate entry 'var__m_sys_hub_step_ext_input_1e53f456db60b380ca7e9c9adb96197e-e' for key 'name'ResolutionThe workaround/fix is to upgrade to New York release and recreate the update set. New York and later releases have a new method of creating update set for flows which should resolve this issue