Aura <force:inputField> is disabled in a custom Lightning component when using custom picklist
Last updated 2017-01-07 ·Reference W-2431963 ·Reported By 28 users
Summary
A <force:inputField> tag used in a custom Lightning component is disabled when using it with a custom picklist field.
Repro
1. Open an org which is a 204 Winter ‘17 release
2. Navigate to Setup -> Customize -> Contacts -> Fields
3. Scroll down to ‘Contact Custom Fields & Relationships’
4. Click ‘New’
5. Choose ‘Picklist’
6. Click ‘Next’
7. Put in the field label ‘Test_Picklist’
8. Check the radio button ‘Enter values for the picklist, with each value separated by a new line.’
9. Add in some dummy values
10. Click ‘Next’
11. Open the Developer Console by clicking your name in the top right and choosing ‘Developer Console’
12. Click File -> New -> Lightning Application
13. Give it a Name and click ‘Submit’
14. Add the following code to the .app file, replacing all text in the file:
<aura:application >
<c:CustomPickListTest />
</aura:application>
15. Navigate to File -> New -> Lightning Component
16. Give it a name and click ‘Submit’
17. Copy the following code into the .cmp file, replacing all text in the file:
<aura:component >
<aura:attribute name="contact" type="Contact" default="{ 'sobjectType': 'Contact' }"/>
<force:inputField aura:id="contactName" value="{!v.contact.Test_Picklist}"/>
</aura:component>
18. Preview the application and note that the picklist is disabled and displayed as --None--
Workaround
There is currently no workaround
Reported By (28)













Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.