2

When deploying a change set, I am getting "Bad boolean filter input." error. All milestones are included and this is the only error out of a changeset with 1500 components.

Can't find anything online related to this, a google search for "Bad boolean filter input." doesn't return anything.

Change Set Screenshot

3
  • Are you doing something like deploying a report that uses a field that is not in the change set?
    – Jagular
    Dec 22, 2014 at 15:44
  • Try using this search engine that's salesforce specific: findsf.info
    – crmprogdev
    Dec 22, 2014 at 16:30
  • @Jagular - all reports have deployed fine, it's just the entitlement processes that have failed.
    – Dawid
    Dec 22, 2014 at 20:56

3 Answers 3

3

In case anyone needs this, your Milestone Criteria in the Entitlement Process cannot have the advanced filter logic for the change set. If there is advanced filter logic, the change set will fail. Just create the Milestone Criteria with all ANDs (no filter logic) and then when you get to production, change to the filtering (AND / OR) that you need.

2

The error was caused by referencing a picklist value in the exit criteria of the Entitlement Process that didn't exist in the target org.

0

I find that the scope of this known issue is broader than described in the KI. Complex filter logic in entitlement process makes process undeployable to target orgs.

The KI suggests ambiguously that filters on Case Record Type are the issue, or that the filters 'contains' and 'does not contain' are to be avoided. The error message 'Bad Boolean' appears.

However I find that straightforward logic like (1 AND 2) OR (3 AND 4) throws this message and deployment fails, with both change sets and the Force.com IDE.

3
  • This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review Mar 23, 2016 at 20:08
  • It does not provide an answer, but it provides significant clarification to an relevant Known Issue which suffers from ambiguity and a misleadingly narrow scope. Mar 23, 2016 at 21:17
  • "To critique or request clarification from an author, leave a comment below their post" Mar 23, 2016 at 21:17

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .