5

I cannot save workflow formula with this line:

INCLUDES(Account.Categories__c, Category__c)

Categories__c is a multiselect picklist and Category__c is text field.

Error says:

Field Category__c is a picklist field. Picklist fields are only supported in certain functions.

And other try:

INCLUDES(Account.Categories__c, TEXT(Category__c))

Error says:

Error: Incorrect parameter type for function 'INCLUDES()'. Expected Text Literal, received Text

Improve this question
3
  • Why can you not save it? If you get an error message, always include it here verbatim.
    – Adrian Larson ♦
    Commented Jan 19, 2017 at 16:08
  • @AdrianLarson just added
    – Vladyslav K
    Commented Jan 19, 2017 at 16:09
  • Formulas are rather limited. This is one of those few scenarios where you might consider a trigger instead.
    – sfdcfox ♦
    Commented Jan 19, 2017 at 16:39

2 Answers 2

Reset to default
3

The brutally inefficient workaround would be to check the categories one by one and use a text literal for each:

0 < CASE(Category__c,
    "Value 1", IF(INCLUDES(Account.Categories__c, "Value 1"), 1, 0),
    "Value 2", IF(INCLUDES(Account.Categories__c, "Value 2"), 1, 0),
    "Value 3", IF(INCLUDES(Account.Categories__c, "Value 3"), 1, 0),
    "Value 4", IF(INCLUDES(Account.Categories__c, "Value 4"), 1, 0),
    "Value 5", IF(INCLUDES(Account.Categories__c, "Value 5"), 1, 0),
    0
)
Improve this answer
4

Includes is looking for a specific text value. "text". That's the 'Expected Text Literal' part of your error. You're trying to pass off the value of a field as text and you cannot do that.

A better way to write this is:

Includes(multi_picklist__c, "value")

Help article describing it here

The text_literal expression must be of type text and enclosed in quotes. It cannot be a merge field or the result of a function. Salesforce returns an error if any of the following occurs: You do not provide a text_literal expression. You provide an empty text_literal expression, such as "" or " ".

Improve this answer
2
  • That explains why the error was encountered, but not a viable workaround. OP still needs to get Category__c in there somehow.
    – Adrian Larson ♦
    Commented Jan 19, 2017 at 16:21
  • @Vladyslav Kushney what are you trying to accomplish? Maybe there is a different approach that we can do that does not use includes.
    – Dan Wooding
    Commented Jan 19, 2017 at 16:26

You must log in to answer this question.

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