Lookup List (Data Pair)Last Updated: 09/06/2018 Introduced in Version: 3.5
Lookup list Data Pairs are used to search for a specific set of data that can be accessed and used within a Flow or a Rule. This tutorial demonstrates how to create and use Lookup Lists in Decisions. The Lookup List Feature allows the designer to create specific System Constants and get the value of an Object by a defined key. Each entity in the Lookup List is represented as a key with an attached value (data pair). In the example below the key will always correspond with the value. The value can be any Type (for example it could be a complex Account Type).
For more information about Integrating with an External Database with a Flow for the purpose of using as a table when creating a lookup List, go to the attached link: Integrating an External Database with a Flow.
The Data Table (Mock Data) has a table called product table that already has two Table Fields. One called Product Name and the other called Product Number are selected. When creating this Database integration one of the Table Keys must be selected. This table has the Product Number selected and these properties will show up in the defined flow steps.
Start by navigating to System > Designers > Lookup Lists and Constants. Locate the Add Lookup List Flow action button and then choose Lookup List Flow (Data Pair) to create a Lookup List, (Figure 1).
This example integrates with a database table that has been previously set up in Decisions. In the Lookup List Flow, start by getting data from the Steps Tab, locate Integrations >My Integrations >Database >Mock Data>dbo.ProductData (Table) category. Locate the table needed to create the data pair list and select Get all from dbo.ProductData Step. Add the step to the flow (Figure 2).
Note: A table can be created from a database, and excel file, or from creating a list of constants, etc.
Next, locate Data>List>List Mapping Step from the Steps Tab and add or drag and drop step onto the flow designer.
Connect the pathways from the Get all from dbo.ProductData. Map the Done pathway to the List Mapping Step and then map the Failed pathway to the End Step. Run the flow in the debugger to verify that is set up properly. The two field names appear in the view Input/Output as the Product Name and Product Number (OutputValue).
This completes the Lookup Lists and Constants Flow example.