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

List of  sObject

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.

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.

Save the form and create an Attached Form Request.

2. Configure FLOW to process Lookup Childs after Submit #

Create New Resources to handle Lookup Childs in Transient: 

• ‘transientFields’ to get all transient fields after submit:
  
  
• Loop over ‘transientFields’:
• 
• 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):
   

  

• Create new resource to collect filtered lookup childs (any label):
  
• add every filtered item to new collection:
  
• For other transient fields use the same logic and create separate collection if you going to process them also:
  
• 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;