My reading of the lightning:inputField and related lightning:recordEditForm docs is that the record is read and written based on the Id supplied via the recordId
attribute. There is no option to bind to a record that has already been loaded as lightning:input does via its value
attribute. This makes lightning:inputField
unusable in pure client-side logic where changes in one place are reflected in other places on the screen without round trips to the server.
So it appears that there is still no way to create input fields (or output fields) that are bound to the SObject metadata so saving a lot of tedious programming work (as lightning:inputField
is) yet manipulate existing client-side data (as lightning:input
does).
Or am I missing something here?
(For me leaving out the recordId
as described in the help like this:
To create a record create layout, use this component with lightning:recordEditForm and pass in the object API name of the record you're creating.
results in no fields being displayed.)