Templates causes conflict on the form when a field used in the template is deactivatedDescriptionThis issue arises when templates are utilized, resulting in conflicts within the form when a field used in the template is deactivated. Although the custom field is absent in the template form, it remains present in the XML of the template. It is important to note that this problem does not occur when the field is completely deleted.Steps to Reproduce Create a new Dictionary entry on the incident (any) table.Create a new template (sys_template) on the incident and use the above field.The newly created field is auto-added to the incident form > apply the template > it works fine.Now deactivate the field and notice the template form and incident form removes this field.Apply the template to an incident and notice it shows a conflict error for the above field, although this is deactivated. NOTE: Please deactivate the field. When you delete it works fine, Issue only when you deactivateWorkaround This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available.Related Problem: PRB1683786