Filter with invalid operators are allowed to be saved during Entitlement Process creation and causing Bad boolean filter input error when deploy
Last updated 2021-11-10 ·Reference W-2875808 ·Reported By 35 users
- For the Case: Case Record Type Field the supported operators are only "equals to" and "not equals to". All other operators are not allowed. This validation is done when we are validating the Inbound Change list, but is ignored when creating the Entitlement Process.
- Actual Result: User is able to create Entitlement Process with invalid operators in filters, which fails only when validating the inbound changesets later. "Bad boolean filter input." error during changeset validation does not allow user figure out the actual cause.
1. Create an Entitlement Process and added a filter: (Case exits the process --> Based on custom criteria Case: Case Record Type does not contain Test 1 ) and click on Add Filter Logic.
2. Create an Outbound change set and added newly created Entitlement process and uploaded to target org.
3. In the target org, from inbound changeset, Click on Validate and it fails with an error "Bad boolean filter input"
Avoid using the filter "Does not Contain"
Reported By (35)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.