Template Applied with 1 conflict - Assigned to

[steveleachman]

I have a user who has create a template which sets, amongst other things, the Assignment group and Assigned to fields on a new incident record. 

However when applying the template they get an error message  

Template Applied with 1 conflict

 Unable to update field"Assigned to"

I think the simplest answer here is that the template can't apply the Assigned to because it cannot validate against the Assignment Group because the changes are being made at the same time.  However, the user is adamant that this template was working until very recently.  Coincidentally, or not, we very recently upgraded to Paris.  

Has anyone else seen this and does anyone know of a solution?

[ccajohnson]

Without knowing how the template is configured, we cannot try to replicate this issue. Have you tried impersonating this user in a sub instance and trying the template? Have you tried the template yourself?

[steveleachman]

Thanks for your response.

The template is pretty basic, it populates some mandatory fields, Caller, Category and Business service and then the Assignment group and Assigned to.  

The template works fine for both the user and myself if the Assigned to field is removed from it.  Fails for both of us if it is put back in.  

This also isn't just one template, we have both created brand new ones and the same error occurs. 

[Tiago Silva]

@steveleachman

Did you had any resolution on this? I am having a similar behaviour in one of my templates, instead, with the category field.

Best regards,

[steveleachman]

No sadly not.  The end user just created a template to populate the fields it could and then does the other part manually. 

We even just reduced the template down to just populating the Category, Assignment group and Assigned to fields and still had the same issue.