---
title: FORM Butler – Process Lookup Childs in FLOW
description: "### **1. Configure Lookup Childs in Editor**   If you want to use Lookup childs, in Editor required to fill appropriate settings:  - Data Sources;  - Field API Name;  - Transient -> true  - Key (autofill automatically, shouldn't change); First of all, if you want to use lookup fields in…"
url: "https://pdfbutler.com/academy/form-butler-academy/form-butler-web-forms/form-butler-process-lookup-childs-in-flow/"
updated: "2026-03-30"
category: Web Forms
---

# FORM Butler – Process Lookup Childs in FLOW

### **1. Configure Lookup Childs in Editor**

 

If you want to use Lookup childs, in Editor required to fill appropriate settings: 

- Data Sources; 

- Field API Name; 

- Transient -> true 

- Key (autofill automatically, shouldn't change);

First of all, if you want to use lookup fields in your Web Form, you must include them in the SOQL query of the Data Source  

**Single sObject**

![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture50.png)

**List of  sObject
 ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture51.png)**

**Note****: ***When submitting related fields from the Webform (for example, **Parent.Name**), only **one-level relationships** are supported.*

This means users can use the following format: 

- Parent.FieldName  

However, deeper relationship paths are **not supported**, such as: 

- Parent.Owner.Name  

- Parent.Account.Name  

- Parent.Owner.Manager.Name  

If a field path contains more than one relationship level, it will be rejected and will not be processed. 

Go to the editor and add this field to the layout.
 ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture52.png)

**Note:** *You should enable Transient for the lookup field so the logic works correctly, but you should not change the key. If you change the key, the logic will not work.*

Add a Dynamic List to the layout, add the required lookup fields, and enable Transient for the logic to work correctly.

![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture53.png)

Save the form and create an Attached Form Request.

 

### 2. Configure FLOW to process Lookup Childs after Submit

![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture54.png)

 

Create New Resources to handle Lookup Childs in Transient: 

- **‘transientFields’ **to get all transient fields after submit:
   ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture55.png)
   ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture56.png)
- Loop over ‘transientFields’:
- ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture57.png)
- Filter transient fields and separate Lookup childs (contains dot (“.”) in key) and other transient fields using formula, where !Loop_over_Transients is Current item from Loop over Transients (Label can be changed by you here):
   ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture58.png) 
  ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture59.png)
- Create new resource to collect filtered lookup childs (any label):
   ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture60.png)
- add every filtered item to new collection:
    ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture61.png)
- For other transient fields use the same logic and create separate collection if you going to process them also:
    ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture62.png)
- And in the end, call Apex class **‘Handle Transient Lookup Fields’, and **Set Input Values: 
   - For the “**fields” **– new created collection (**‘transientFieldsHasDot’ **in this example); 
   - For the “**recordId**” - standard recordId variable;
   ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture63.png)
   ![](https://pdfbutler.com/wp-content/uploads/2026/03/Picture64.png)