Apparently there are no known cases of force:inputField working correctly. @Fab asked this question 9 months ago, and noone seems to have been able to get it working. I guess for now the best option is, like @Mohith suggested here and @Jenny commented above, to create your own lookup component.

https://developer.salesforce.com/blogs/developer-relations/2015/06/salesforce-lightning-inputlookup-missing-component.html

I hope this will be fixed and working asap, as it's pretty hard to have users create sObjects without it.

EDIT

As @Peter posted on the thread linked above, there is currently a limitation in force:inputField's that you are required to add a default attribute like so:

default="{ sobjectType: 'Account' }"

Apparently there are no known cases of force:inputField working correctly. @Fab asked this question 9 months ago, and noone seems to have been able to get it working. I guess for now the best option is, like @Mohith suggested here and @Jenny commented above, to create your own lookup component.

https://developer.salesforce.com/blogs/developer-relations/2015/06/salesforce-lightning-inputlookup-missing-component.html

I hope this will be fixed and working asap, as it's pretty hard to have users create sObjects without it.

EDIT

As @Peter posted on the thread linked above, there is currently a limitation in force:inputField's that you are required to add a default attribute like so:

default="{ sobjectType: 'Account' }"

Apparently there are no known cases of force:inputField working correctly. @Fab asked this question 9 months ago, and noone seems to have been able to get it working. I guess for now the best option is, like @Mohith suggested here and @Jenny commented above, to create your own lookup component.

https://developer.salesforce.com/blogs/developer-relations/2015/06/salesforce-lightning-inputlookup-missing-component.html

I hope this will be fixed and working asap, as it's pretty hard to have users create sObjects without it.

Apparently there are no known cases of force:inputField working correctly. @Fab asked this question 9 months ago, and noone seems to have been able to get it working. I guess for now the best option is, like @Mohith suggested here and @Jenny commented above, to create your own lookup component.

https://developer.salesforce.com/blogs/developer-relations/2015/06/salesforce-lightning-inputlookup-missing-component.html

I hope this will be fixed and working asap, as it's pretty hard to have users create sObjects without it.

EDIT

As @Peter posted on the thread linked above, there is currently a limitation in force:inputField's that you are required to add a default attribute like so:

default="{ sobjectType: 'Account' }"