clefsrud
26 posts
Registered:
24 Nov 2014
Answered
29 Apr 2015
in reply to
Missing user
My specific situation is that I have a workflow rule that is trigged by a change in a lookup field (contact) on the lead record. In the portal, I have a lead edit form which includes this lookup field to which changes may be made. However, when a change to a record is posted to CRM from the portal, all fields on the portal form are 'changed' in CRM, whether or not the user actually altered the value. Therefore, my workflow is triggered every time any change is posted; lots of false positives. I asked a question in this regard in a previous thread.
So I was attempting to flag when a change was truly made to my lookup field, and include this flag in the operation of the workflow. By definition, the lookup field is set to the current user's contact (i.e. they can only see records that have been assigned to them). So, my logic was simply to compare the guid of the lookup field value to the user's 'CRM Contact Id' guid, then set the flag accordingly to either trigger the workflow (if guids different) or not (guids the same).
Since I cannot do this, I have implemented a goofy alternate that works accepatably.