When passing lists of records into connectors which accept list inputs, it would be great to be able to add a formula onto the source list, rather than passing the full list. The main scenario I see value for would be using the "where" formula.
Here's an example use case:
Background:
- I'm integrating employees from my HRIS to my ERP.
- I have a complete list of employee changes from my HRIS and a complete listing of my existing ERP records.
- I want to first create all employees which do not yet exist in my ERP, and then do an update on all other employees.
I have a field in my list which says 'create' or 'update'. When creating my API call to send into the ERP tool, I'd like to pass all records where the field says 'create' into my message template to create my complete set of API functions. Then I'd create another message for records that say 'update'. If I want to process it this way currently, I'd have to make two different lists, a 'create' list, and an 'update' list, rather than keeping all of my data in just one list.
Similarly, another use case would be if I want to send data from a list into a callable recipe only where it meets certain criteria. I shouldn't need to loop through my original list and create a completely separate list in order to pass a subset of a list into another tool.
Amy Jorde
Allow formulas on list inputs
When passing lists of records into connectors which accept list inputs, it would be great to be able to add a formula onto the source list, rather than passing the full list. The main scenario I see value for would be using the "where" formula.
Here's an example use case:
Background:
- I'm integrating employees from my HRIS to my ERP.
- I have a complete list of employee changes from my HRIS and a complete listing of my existing ERP records.
- I want to first create all employees which do not yet exist in my ERP, and then do an update on all other employees.
I have a field in my list which says 'create' or 'update'. When creating my API call to send into the ERP tool, I'd like to pass all records where the field says 'create' into my message template to create my complete set of API functions. Then I'd create another message for records that say 'update'. If I want to process it this way currently, I'd have to make two different lists, a 'create' list, and an 'update' list, rather than keeping all of my data in just one list.
Similarly, another use case would be if I want to send data from a list into a callable recipe only where it meets certain criteria. I shouldn't need to loop through my original list and create a completely separate list in order to pass a subset of a list into another tool.
3 people like this idea