Dynamically Required Picklists to Capture...
Mar 23, 2006There have been some really interesting best practice ideas emerging from customer and partner blogs. This week Scott Hemmeter wrote about how you could use dependent picklists to create dynamically required picklists.
The example he used was a field to capture reason lost, a field that often appears on the opportunity page layout. Are you loosing deals based upon company viability, features, price, lack of references? This is valuable information. The challenge that most companies face is that they can’t make it a required field because the rep won’t know the reason for the loss until it’s closed. On the flip side they can’t ensure that it’s filled out consistently without it being a required.
His simple solution makes the reason for a loss required only when the stage is equal to closed lost. To learn how it’s done, visit Perspectives on Salesforce. Scott great work!


Any ideas on how I could create an "action" dependency? I'm trying to create a calendar event when a status field is set to "confirmed"
Posted by: jamie | March 29, 2006 at 11:56 AM
Jamie, have you tried setting up workflow rules?
Posted by: Kingsley | March 29, 2006 at 12:41 PM
Good article!
Further to this, is it possible to create dependent field which is currency/text format? For example, if the reason lost is "other", then there will be a required dependent text field "Pls provide details"; or if the reason lost is "Price", then there will be a required dependent currency field "winning price (price of the final deal)".
I dont understand why the dependent field can only be picklist.
Any comments?
Posted by: Chuankai | April 11, 2006 at 09:03 AM