# How to pass a field from the main flow to a lookup step

**URL:** <https://community.synatic.com/t/how-to-pass-a-field-from-the-main-flow-to-a-lookup-step/216>\
**Category:** Flows\
**Tags:** helper-functions\
**Created:** [April 25, 2022, 9:45am UTC](https://community.synatic.com/t/how-to-pass-a-field-from-the-main-flow-to-a-lookup-step/216 "2022-04-25T09:45:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![navessa](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.synatic.com/navessa/32/58_2.png) [@navessa](https://community.synatic.com/u/navessa)\
**Post date:** [April 25, 2022, 9:45am UTC](https://community.synatic.com/t/how-to-pass-a-field-from-the-main-flow-to-a-lookup-step/216/1 "2022-04-25T09:45:15Z")

</div>

To pass a field from the main flow to a lookup step, “ **{{record.fieldname}}** ” is used.

**NB: “{{record.fieldname}}” is used to pass the current record before the lookup step. This can also be used if there are more than one control step.**

Illustrated in the below image is an example of a SQL Server lookup step where “task\_ID” is a field from the main flow that is being used in the lookup step.

![image](https://canada1.discourse-cdn.com/flex032/uploads/synatic/original/1X/9fd097b3c3186cdf54050fffbed03a1f99079a50.png)

[How to pass a field from the main flow to a sub-flow or to a control step](https://community.synatic.com/t/how-to-pass-a-field-from-the-main-flow-to-a-sub-flow-or-to-a-control-step/214)