Dynamics GP - Error after upgrade "Trigger is not registered"

https://blogs.msdn.microsoft.com/developingfordynamicsgp/2012/01/31/quick-tip-solving-dexterity-trigger-clashes/

• This problem occurs due to GP customizations that are triggering multiple code units on the same event
• Changing the order of the customized dictionaries in the Dynamics.set file will ensure the triggers are loaded in the correct order
• Disable dictionaries in your dynamics.set one by one and try launching GP to determine which dictionary is causing the trigger error
• Once you figure out which dictionary is causing the error, Edit your Dynamics.set file, and move the offending dictionary up so that it loads first