Knack Flows Searching & Bulk Actions Frequently Asked Questions
- How do I use the “Search for a Single Record” action?
- What should I do after using the “Search for Multiple Records” action?
- How does “Search by Record ID” work?
- Can I perform bulk actions using the Knack connector?
- What happens if the search returns no results?
- What is the difference between "Search for a Single Record" and "Search for Multiple Records"?
- Can I use multiple operators in the "Search for a Single Record" action?
- How do I act on multiple records returned by the "Search for Multiple Records" action?
How do I use the “Search for a Single Record” action?
The “Search for a Single Record” action retrieves one specific record based on criteria, such as a unique identifier. There's no need to use the Iterator tool step after! This is ideal for follow-up actions targeting individual records.
What should I do after using the “Search for Multiple Records” action?
Typically, the next step is to add an Iterator to loop through each returned record, allowing you to process them individually.
How does “Search by Record ID” work?
This action looks for records using their unique Record ID. It’s useful for linked data scenarios, such as finding related records based on a connection field.
Can I perform bulk actions using the Knack connector?
Bulk actions are not directly supported, but you can use tool steps like the Aggregator tool combined with other actions to perform bulk operations more efficiently.
What happens if the search returns no results?
If no records are found, subsequent steps may not execute. You can add error-handling steps or conditions to manage scenarios where no results are returned.
What is the difference between "Search for a Single Record" and "Search for Multiple Records"?
The "Search for a Single Record" action retrieves only one record, whereas the "Search for Multiple Records" action retrieves an array of matching records. The single record search is used when you expect one result, while the multiple records search is for handling larger datasets where you may need to iterate through several records.
Can I use multiple operators in the "Search for a Single Record" action?
No, you can only use one operator per search step. For example, if you use the “contains” operator, it will apply to all fields being filtered. If you need to apply different operators, you will need to create separate search steps.
How do I act on multiple records returned by the "Search for Multiple Records" action?
When using the "Search for Multiple Records" action, the returned data will be an array of records. To act on each record, you should use an Iterator step after the search step. The Iterator allows you to loop through the array and perform actions on each individual record, such as updating fields or sending notifications.