#Multi-picklist Field0 personne en discute

For me this case is even more weird there is a  multi select picklist list field called " Brand__c" in account layout however this field doesn't even exist in opportunity/lead/contact object and i am still getting an error saying "The lead conversion failed because the value for the field Brand__c is invalid. The value comes from the lead field that's mapped to the field Brand__c. Ask your admin to check the field mappings." I checked the mappings and there is no such field mapping that can be found in the lead mapping. What could be the issue please help. #Trailhead Challenges#leadconversion #Convert Lead #Flow #Custom Buttons #Multi-picklist Field #TrailblazerCommunity

Hi ,

AND(
INCLUDES(OTHER_Features__c,"BODY"),
ISBLANK(TEXT(BODYs__c))
)

Hi Cindy,

MS Picklists are a real pain to work with...

I've used a workaround before with a little help from @Steve Molis:

Create a Long Text Area field on the object (doesn't need to be on the page layout)

In the process builder, keep your criteria.

Add a record update for the record that triggered the process and select:

Field: Long Text Area Field

Type: Field Reference

Value: [Object__c].MS_Picklist__c

Add a second record update  for the record that triggered the process and select:

Field: MS Picklist

Type: Formula

Value: [Object__c].LongTextArea__c+";X;Y;Z"

Save and activate

Hi Fernando,

When you say distributed in 3 level, do you mean across 3 fields and all the 3 fields are MSP Fields?

What are the number of values n each of the MSP field?

Anyway if you had few values and in order to search for a MSP fields this is what you have to do

Create a Custom Long Text field and using a workflow or process builder update the custom field with the values from the MSP field.

This is how the workflow configuration will look like

Create a custom long text field on the object

create a workflow rule on the object

evaluation criteria: created and everytime its edited

rule crtieria: formula evaluates to true and the formula is

NOT(ISBLANK(MSP_Field__c))

use the insert field button to select the field API Name of the MSP field

Immediate Action: Field Update

Field to Update: Long Text field

use formula to set the new value and the formula is

IF(INCLUDES(MSP_Field__c, 'Value1'), 'Value1', NULL) + ' ' +

IF(INCLUDES(MSP_Field__c, 'Value2'), 'Value2', NULL) + ' ' +

IF(INCLUDES(MSP_Field__c, 'Value3'), 'Value3', NULL) + ' ' +

IF(INCLUDES(MSP_Field__c, 'Value4'), 'Value4', NULL) + ' ' +

and so on

IF(INCLUDES(MSP_Field__c, 'Value25'), 'Value25', NULL)

Save,Done and Activate the Workflow rule

In Salesforce all Text fields are included in the search

- this has been a long standing request as you'll notice from the link I provided. There is a lot to making this an available functionality as it is a more complex search from a database / referential / indexing perspective which is likely one of the reasonings as to why it is not a capability yet.

Idea:

Crea los 3 pick lists as defined above, and another field que es de texto pero con FLS de solo lectura y escondido en los page layouts (nota, esto no puede ser un campo formula por que necesitamos que el valor sea guardado). Despues creas un Workflow Field Update o un Lightning Process que cuando el caso es saved guarde este valor en el campo:

ValorPicklist1 & " - " & ValorPicklist2 & " - " & ValorPicklist3

Una vez este valor este guardado los usuarios podrán buscar los casos con búsqueda normal de texto.