I have a lightning component that uses force:inputField for a handful of Contact fields in a form in a Partner Community so that a logged in user can update their contact info. It appears that if the field did not previously have the value (eg. the "Title" field is null when the page loads) then it won't let me add a value. However in the Sandbox I can.
I have the page set up like this (abbreviated for clarity):
<aura:component controller="CommunityController" access="global">
<aura:attribute name="contactId" type="Id" />
<aura:attribute name="contactRecord" type="Contact" default="{ 'sobjectType': 'Contact' }"/>
<force:inputField value="{!v.contactRecord.Title}" class="inputFeild"/>
<ui:button class="slds-button slds-button--brand" label="Save" press="{!c.saveContactRecord}"/>
</aura:component>
So in the sandbox, if I load this component and the Contact did not have a Title, I can add one and when I submit the form, I can do console.log(component.get('v.contactRecord));
and I see that the contact has a value set to what I entered.
In Production, when I do the same, the Title attribute does not appear on the contact. HOWEVER, if the Title has a value when the component is loaded, I AM able to change the existing value in Production...
Is this another force:inputField bug?
EDIT: This appears to also happen with regular ui:inputText and other ui tags. If the value isn't set when the page loads, then it's not letting me set a value and send it back to apex. Again, this also works in sandbox but not in Production.