I recently ran into a situation with a client who wanted to send texts to the parents of children in his camp. Problem is, when we queried the data, we returned records for children, some of which had the same parent. Sending to all of the records meant that some parents would receive multiple texts, one for each child they had enrolled in the camp.
Well obviously, this is not an ideal situation, a parent only needs one broadcast text message regardless of how many kids are at the camp.
So, I created an inline dynamic filter system using Data Store and a standard Make filter.
The Data Set
As you can see in our sample data set, we have 9 student records, but three of them are duplicates (highlighted colors indicate duplicates).
The desired outcome is to send 6 text messages to 6 parents, not 9 text messages to 6 parents.
How Does the Dynamic Filter Work?
The dynamic filter builds or grows as each record is processed. The filter values use a unique value, in this case the phone number, to build the filter with each bundle that is retrieved from the data source.
The dynamic filter utilizes a single record in a data store. I often have a data store where I save variables from multiple random scenarios. In this case, I have a data store where multiple single records are reused in multiple scenarios.
I create a single text field, called “Variable Value” and manually create the key, like “DynamicFilter1.” Then I always use the the Data Store record that has “DynamicFilter1” as the key for a particular scenario.
Here is the data structure for my variable data store:
There are Three (3) Data Store Modules Used in the Dynamic Filter System
- Data Store Module #1: Must only be processed 1 time in the scenario.
- Data Store Module #2: Retrieves the current value of the data store record for each bundle processed
- Data Store Module #3: Adds the unique record value to the filter value after each bundles is processed. This module must NOT be after the filter.
Data Store Module #1
Data Store module #1 sits at the beginning of our scenario, and must only be processed one (1) time per scenario run.
This scenario simply clears the record value each time the scenario runs:
Data Store Module #2
Data Store module #2 must be positioned after your data source, and be processed once for each bundle record that is retrieved from your data source. The purpose of this module is to get the latest version of your data store record to be used in the filter that appears before the action step (i.e. send the text in our use case).
The Dynamic Filter
The filter uses the value from Data Store module #2 to filter previously used values. The filter condition uses the retrieved data store value, and only lets values (phone numbers in our case) pass that are not a part of the data store value.
Data Store module #3
Data store module #3 adds the last bundle to the dynamic filter value, taking the retrieved value from the data store record, and saving the just processed unique record value (phone number) to the data store record. I use a comma to separate each of the values.
Each time a phone number is formatted, it is added to the dynamic filter value.
Let’s look at the output of Data Store module #3:
As you can see, with each passing module, the filter value increased by one unique record value (phone number).
After each value was added, the new filter value was retrieved and used in the filter.
When we examine our filter, we can see that three unique record values (phone numbers) did not pass our dynamic filter:
So, in the end our parents only received 1 text, regardless of the number of children they had at the camp.
This isn’t a filter system that I use regularly, but it has come in handy many times.
Do you have a situation where you might use a Dynamic Filter System?
If you get stuck, I’m happy to help you one-on-one!