Ask Search:
LaTashia SmithLaTashia Smith 

We couldn't find the multi-select picklist on the Opportunity object ...?

I am on the Customize a SF Object > Create Picklists and Field Dependencies challenge and am running into this error message. I have checked it over and over and don't see why I am getting the error. User-added image
Best Answer chosen by Jayson (salesforce.com) 
Ron FeherRon Feher
SOLVED; sort of, I deleted the custom object that I had created and when I re-created it, after previewing the functionality of the picklist, it takes you out of lightning and into classic. The first time I escaped and went back to lightning; the second time I stayed in classic and finished the instructions and passed the module. Not sure if the switch to classic mattered but it solved it for me!

All Answers

Arijit MajeeArijit Majee
Hi LaTashia,

From the screenshot, I can see this field is controlled by 'Stage' field. You need to see whether right values are mapped to this picklist. otherwise, this field will come as blank field in the layout.
Amit SinghAmit Singh
Hi Smith,

What exact issue are you facing?
LaTashia SmithLaTashia Smith
The iss that I am facing is that it is saying "We couldn't find the multi-select picklist on the Opportunity object." In the screen shot I provided you can see I have completed the steps and the picklist exists. 

The steps also say:
While still viewing the Opportunity object Fields & Relationships, click the Field Dependencies button.
Click New, and set up the new field dependency.
Select Stage as the Controlling Field.
Select Close Reason as the Dependent Field.
Click Continue.
At the top of the table, click Next until you see the Closed Won and Closed Lost columns.
Double-click inside cells to select the appropriate Close Reasons in the Closed Won and Closed Lost columns.
Closed Won: Select all values starting with “Won”
Closed Lost: Select all values starting with “Lost”
Click Preview, then test the dependency by selecting different stages and viewing the different close reasons available for each stage.
Click Close to close the preview window.
Click Save, and click OK to accept the warning that not all dependent values have been included.

And I have done that as wellUser-added image
Charley HoughCharley Hough
I am facing this same issue. I have a Picklist (Multi-Select) with the label "Close Reason" created on the Opportunity object and also have the dependency setup but I still get the error message. Any suggestions on how to fix this are welcome. Thanks.
LaTashia SmithLaTashia Smith
I wasn't able to get any assistance in the Community so I submitted a ticket via Trailblazer Support. They logged into my Org and moved me past this issue. They didn't say exactly what the issue was (if there was an issue to begin with). Sorry I don't have much else to go off on. 
Charley HoughCharley Hough
Thanks for that tip and the quick reply LaTashia, I will do the same. :)
keerat kapoorkeerat kapoor
I am having the same issue. you can see the screenshot that I do have the Multi-select picklist selected.









User-added image
LaTashia SmithLaTashia Smith
Keerat - 

I wasn't able to get any assistance in the Community so I submitted a ticket via Trailblazer Support. They logged into my Org and moved me past this issue. They didn't say exactly what the issue was (if there was an issue to begin with). Sorry I don't have much else to go off on. 
Charley HoughCharley Hough
I submitted a ticket and someone contacted me but they still have not fixed the issue for me.
LaTashia SmithLaTashia Smith
I had the same issue. I kept emailing them constantly until it was resolved. Unfortunately they do not have a quick turnaround for assisting with issues. 
Ron FeherRon Feher
SOLVED; sort of, I deleted the custom object that I had created and when I re-created it, after previewing the functionality of the picklist, it takes you out of lightning and into classic. The first time I escaped and went back to lightning; the second time I stayed in classic and finished the instructions and passed the module. Not sure if the switch to classic mattered but it solved it for me!
This was selected as the best answer
Nicolás Vásquez MurciaNicolás Vásquez Murcia
Thanks Ron! You're right. All I had to do was deleting the custom field, switch to Salesforce Classic and complete this task again.With this I finally earned the badge.
Shawnee ScesneyShawnee Scesney
Ron, 
This worked like a charm.  Thanks!
Renee RoullierRenee Roullier
LaTashia's issue was the last itme in the picklist had a type. it should have been singular: 
Won: Other Reason