I have a lookup list that I use to look up values that could change, i.e. when an approver leaves the company.
I have a 'Calculated Value' field that looks up an approver's email address from the look up list.
The calculated value field is connected to an 'ApproverEmail' column.
I, then, use this 'ApproverEmail' column value, which is passed on by the calculated field, when sending the email (I am not using quick approval because the approver needs to open the item and approve from there).
My question: What are the pros and cons of getting values from a lookup list using the above approach, as oppose to having a workflow doing the lookup?
Thank you for your input.
Solved! Go to Solution.
Question: If the Approver changes, will the email address be updated? If not, both options would fail. Can you not do a lookup at the time the form being used is created? And the lookup used UserProfileServices or some other source you know will be current.
Thank you for the quick response.
Yes, I will be doing lookups when the form is created, not just for user names or other profiles, but for other fields as well. I might need to look up an external address that cannot be computed by the 'userProfileLookup' function. Is there an advantage or disadvantage of doing this lookup when the form is created as oppose to having the workflow do the lookup doing its run. I am new to Nintex development so I would like to learn some 'best-practices.'
Hopefully a best-practice person will provide some insight here - for myself, if there is no degradation (slowing the opening performance) of doing the lookup when the form opens, I'd rather get the information then (I can verify it loads correctly); the workflow can do other work, as needed, when the form is submitted.