Conflicts in Custom Actions

The conflicts that may arise while performing a Save As on Custom Actions are as follows:

1. 1. The Custom Action details like parameter count, parameter values, Q Class, Q Function etc. in the source or target may have been changed.

Example:

• Project Source has a custom action "CustKey1" and has been copied to Project Target so the Project Target now has the same custom action "CustKey1."
• If the custom action properties like name, parameter count, the object class, static data values of the action have been changed in the Source or Target project and a Save As is performed again, the custom action will not be copied into the target.
  1. Different actions with the same name will show conflict.

Example:

• If Source Project has an action of name "Key1," Target also contains an action named "Key1."
• The source action will not be copied into the target even if these are 2 different custom actions.