Rick, I am not sure if there is any performance gain, but I always go to the database first. Doug
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rick Westbrock Sent: Friday, October 17, 2014 10:35 AM To: [email protected] Subject: Set Field If syntax when matching on another form ** Hi all- I wanted to get feedback on something I remember learning way back in a Remedy class (pre-BMC) in Pleasanton to make sure that I am remembering correctly. I seem to recall that I was told that the best practice when writing the qualification for a Set Fields action from another form that you should use the other form's field before the operator and the current form's field after the operator like this: 'DEPTID' = $DeptID-New$ I thought that this was either more efficient or provided more predictable results (or maybe both). Does anyone else follow this convention? I have run across several instances in some custom workflow where that is reversed and I see $DeptID-New$ = 'DEPTID' which just feels wrong to me. Below is more detail to clarify my examples. Form A: field DeptID-New Form B: field DEPTID There is a filter on form A that does a set fields which reads its value from form B. I believe the proper syntax if I want to match the department ID fields between the forms is this: 'DEPTID' = $DeptID-New$ >From there the set fields action can copy values from the matching record in >form B into the fields of form A. Thanks, Rick _________________________ Rick Westbrock AppOps Engineer | IT Department 24 Hour Fitness USA, Inc. _ARSlist: "Where the Answers Are" and have been for 20 years_ This email is subject to certain disclaimers, which may be reviewed via the following link. http://compass-usa.com/Pages/Disclaimer.aspx. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
