Forums

Submitting unchanged field value triggers CRM workflow Cancel The title field is required!

1. Missing user

   
   17 Apr 2015

   Link to this post

   When a record is updated from the portal to CRM, all fields are 'changed' in CRM whether or not individual field values were actually altered.  I have a workflow in CRM which is triggered by the change in a particular field.  Given these two facts, the workflow is triggered every time a record is updated via the portal, even though the value of my trigger field was not altered.  This is a bit of a problem.
   Is there any configuration option in the portal where the value of a field is not sent in the update if it was not changed (sort of a isDirty concept at a field level)?  Nothing jumps out at me.
   Other options?
   
   Chris Lefsrud
2. Missing user

   
   Answered

   17 Apr 2015

   Link to this post

   Hi Chris,
   
   Unfortunately there is no option for this as of yet natively in TPC however it is slated as a feature in one of our 3.x versions this year. As a work around you could use the concept of data image with your CRM plugin. Here is a link on how it's configured https://msdn.microsoft.com/en-us/library/hh237515(v=crm.6).aspx#bkmk_RegImage.
   
   Thanks,
   Steve
3. Missing user

   
   17 Apr 2015

   Link to this post

   Steve:
   
   This is portal issue as opposed to a CRM issue; the workflows all work perfectly fine when changes to the record are completed directly in CRM.  The problem arises when the record is updated via the portal AND the field value has not truly changed, falsely triggering the workflow.  I should be able to apply some logic in the portal along with a modification of the workflow to counter the all-or-nothing update of the record from the portal.  I was just hoping for a configuration option.
   
   Chris Lefsrud
4. Missing user

   
   17 Apr 2015

   Link to this post

   Hi Chris,
   
   I understand and it is a feature we are implementing in the short term. I was just, as requested, outlining a potential option because it isn't currently a feature within TPC. Hope this helps.
   
   Steve