Data Table Lookup action

Enter the Reference Key value you want to find. 

Note: Click the arrow next to Inputs to expand or collapse the list. The list is always a single item. At runtime, if the value to look up is a NOT_SET string, execution does not take the Failure output. Instead, the system invokes flow error handling.

These outputs allow the flow author to map the custom field values in the Data Table to variables within the flow. 

Note: Click the arrow next to Found Outputs to expand or collapse the list.

These outputs allow the flow author to map the results of any resulting errorType and errorMessage. 

• errorType: A non-empty string that contains the type or category of the error. For example:
  • DataTablesInternalServerError: The system encounters an error while performing the lookup action.
  • DataTablesServerTooBusyException: The system is unable to process the lookup action because the service is too busy.
  • DataTablesSyntaxError: The system encounters an internal error when the call to perform the lookup uses incorrectly formatted data, or when processing the response data encounters an error.
  • DataTablesTableNotFoundException: The data table for which the lookup is being performed does not exist.
• errorMessage: A non-localized failure message. The string may be empty or NOT_SET.

Note: Click the arrow next to Failure Outputs to expand or collapse the list of variables.

This path indicates that Architect found a row in the Data Table that matches the Reference Key Label’s value, and the variables mapped in the Found Outputs are set with the data from that table row. 

Note: Found outputs only populate when the flow follows the Found path.

Drag the appropriate action below the Found path to follow the route you want the interaction to take. For example, an audio prompt, a transfer to the appropriate representative, or a combination of actions that follow your company’s flow design.

This path indicates that Architect did not find the matching Reference Key value specified on the action. 

Note: No Failure or Success outputs populate if the flow follows the Not Found path.

This path indicates that Architect encountered an error while running the action or a problem occurred while processing the results.  

Notes: 

• Failure outputs only populate when the flow follows the Failure path. 
• If the network experiences connectivity issues, the action automatically takes this failure path.

Drag the appropriate action below the Failure path to direct the route you want the interaction to take. For example, a transfer action to send the caller to an agent or representative for assistance.