Take the 2-minute tour ×
Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It's 100% free, no registration required.

I want to be able to have the controlling field of a dependent picklist not show to the users, I am updating this field using workflow.

From Salesforce docs Page layouts Make sure controlling fields exist on any page layout that contains their associated dependent picklist. When the controlling field is not on the same page layout, the dependent picklist shows no available values.

Does anyone know of a good workaround? Not keen to turn this page into Visual Force just for this.

share|improve this question
    
Why are they dependant if you're not planning to show them both on the page? AFAIK, the only use for dependant picklists is to help human input. –  JLiljegren__c Sep 30 '12 at 1:49
    
So you can limit what is in the dependent picklist based on some data that is populated in the back end system –  Kris Moyse Oct 2 '12 at 18:51
    
I see - you're looking to show the controlled field on the page. I read it the other way around. Yeah, that's not possible unless you also have the controlling field on the page as well. –  JLiljegren__c Oct 2 '12 at 18:54
add comment

5 Answers

up vote 4 down vote accepted

Dependent picklists are handled through Javascript on the page, so if the controlling field isn't available, there's no way to handle that functionality. You must be setting that controlling field some other way than through the UI, but I wonder about the usefulness of not being able to create a new record with a non-null controlling field anyway.

The only way I know of to control picklist values, without Visualforce, is through Record Types, which may or may not be a good solution for you.

share|improve this answer
add comment

If the use case is just updating field A based on Field B why not use a field update workflow and hide field B from the pagelayout??

please correct me if I missed something

share|improve this answer
    
Not just updating, updating what can be selected in the dependent picklist based on data in another field that is driven by a back end system. –  Kris Moyse Oct 2 '12 at 18:52
add comment

The controlling field can be made hidden on the page. For example,

So that both controlling field and dependent picklist are on the same page but yet controlling field not visible/available to change for the user.

share|improve this answer
1  
That would be nice but unfortunately it doesn't work - if you hide the controlling field, the controlled field becomes readonly. –  Marc Jan 25 '13 at 12:40
add comment

How about make the controlling field read only on the layout and relegating it to the System Information or a similar section?

share|improve this answer
    
That is what I have done so far but we are trying to take off all system fields off the screen. The customer doesnt want to see anything that is not relevant to them. –  Kris Moyse Sep 29 '12 at 23:22
    
Nice idea @techtrekker, unfortunately salesforce always shows the controlling field next to the controlled field if you use inline editing. –  Marc Jan 25 '13 at 12:41
add comment

Out solution currently is just to accept that the controlling field is visible and editable but to have a validation rule (ISCHANGED) which does not allow it to be changed. This is an option when you set the controlling field value once at creation and it should never again be changed.

You can also make the controlling field readonly for certain profiles under "Security Controls" -> "Field Accessibility". Removing it makes the controlled field readonly :-(

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.