Why would a field be unavailable to me in Process Builder? - Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
Brian BoyleBrian Boyle 

Why would a field be unavailable to me in Process Builder?

Opportunity>Closed Lost Reasons (picklist) is not available in my list of fields.  Permissions seem to be right--I can see the field in layout/edit mode, etc. and so can my users. 
Deepak AnandDeepak Anand
If the Process is on the Opportunity and if the field being updated is on the same object then selecting the field on the same object can be a little tricky. 
User-added image

And then you should see this - 
User-added image

Worth voting: https://success.salesforce.com/ideaView?id=08730000000DkFTAA0
David HindmanDavid Hindman
Is that a dependent picklist? That may be a factor...
Brian BoyleBrian Boyle
Hey Deepak and David - Not a dependent picklist.  Deepak I see all the other fields (including other picklists on the Opp object!) which is why it's so strange.  And I'm not trying to update a field--just spawn a Chatter post.
Brian BoyleBrian Boyle
David I take it back--it IS a dependent picklist, but it's dependent on Stage (Closed Lost = Closed Lost Reasons) . . . 
Brian BoyleBrian Boyle
If process builder's not an option--how would I post to Chatter ONLY when the opp is Closed Lost and Closed Lost Reasons/Closed Lost Competitor and Closed Lost Comments are populated (all required via VR when Stage = closed lost).  Anyone have any ideas?

Basically we want to avoid posting old information--my reps are updating old opps.  Maybe there's something I can do to say only post if it's an opp that's been created in the last 6 months or something?
Jackie DoanJackie Doan
You can use process builder to evaluate an opportunity every time it's edited, and visual workflow to create the chatter post. Your flow has the ability to evaluate the appropriate criteria for posting to chatter, or just ending the flow if the record should not post. 

Take a look at this idea - In it, I show how to create a chatter post within flow.