Forums

Exclude some fields from being submitted Cancel The title field is required!

1. Kerillos Kamel

   

   17 posts
   Registered:
   24 Jun 2022
   06 Mar 2023

   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)?
   Other options?
2. Rawdon Edghill

   

   76 posts
   Registered:
   16 Dec 2020
   06 Mar 2023

   Link to this post

   Hi Kerillos,
   
   Unfortunately, there is no configuration option in the portal to send any changed fields in the update request to CRM. When a record is updated, the portal sends the entire record to CRM, and all fields are marked as changed in CRM, even if their values have not actually been altered. You may have to add additional logic to actually check old value and new value and if they are different then run your workflow. If they are the same then you would do nothing.
   
   I hope this information helps.
   
   Regards,
   Rawdon