Include logic operator choices in Data Deployments
Currently Data Deployments only allow filtering on
[FIELD] = [VALUE]
It would be beneficial to be able to include other logic operators such as:
We’ve made lots of improvements to the data deployment filters over the past few months.
The filters now include:
- not equal
- greater than (or equal to) & less than (or equal to) for dates, datetimes and numbers
- is empty & is not empty for nillable fields
You can now specify multiple values (use OR logic) when using the equals filter.
We’ve made it easier to input dates and times so that you don’t have to rely on knowing the exact format.
There’s validation so that filters with invalid values aren’t possible. These invalid values would have caused the deployment to fail.
If there’s still further improvements that you need, please could you create (or vote on) a new idea? This will help us identify which improvements are most valuable to you.
AdminGearset Team (Admin, Gearset) commented
We've now also released support for multiple criteria logic (OR).
Marc D Behr commented
I too would like to see filter logic added to the selection criteria (rather than just AND's)
Nicolas COMMEAUX commented
Would also be very thanksfull to handle multiple criteria with filter logic such as "1 AND (2 OR 3)" as it exists in Salesforce.
Also would love for a "case-insensitive" flag or something... or the ultimate regex expressions :D
The basic set for such filters I would wish for is what we're used to from https://workbench.developerforce.com ... That is:
in (comma separated list)
not in (comma separated list)
Evan Clarke commented
As it stands right now, data deployments are essentially worthless to my company as we need to be able to specifically filter out records owned by a (system) user for our data deployments.