This is really an EF Code First question, but sometimes the context of OData makes a difference. The question is simple. Our underlying SQL Server tables/views have Identity columns as the (surrogate) primary key. They also have a ‘code’ field which represent unique identifiers which users are familiar with. Simple example: CarModel: Id = 3, Code = ‘Ford’;
I have successfully create the EF Mode and OData to navigate using the ‘Code’ field as the navigation key, using Data Annotations, and the underlying tables/views have indexes on those columns, so this is acceptable. But I would really like to have the Id column as the key, and as the navigation property in the model, but not have it show up in the response. Perhaps this is where the OData part makes a difference, because I would prefer not to do any complex interception and re-shaping of the response. Setting the columns to ‘private’ or even ‘internal’ throws an error during model generation: ‘Table X has no key defined’
Is it possible to define an identity column in the EF Model, but not have it part of the OData entity/response?
Edit:
So, my comment below is still valid. This is both not a good idea for identity/key columns, nor would ‘hiding’ them allow the model to compile correctly. However, thanks to some links from @mreyeros and a social.msdn post from Vitek Karas, here are some notes.
The System.Data.Services namespace has an IgnorePropertiesAttribute. It allows properties in your model to be ‘hidden’. However, as Vitek says, it currently only works with the ReflectionProvider, not with EF. (And you need to make sure you are referencing the correct library if you are using a NuGet managed release.
That said, the fluent configuration API will work in EF/OData:
modelBuilder.Entity<Foo>().Ignore(f => f.Password);
However, not only does it hide a property in the response, it also hides it from the model and the database (which might be okay for read-only query models). So if you mark a navigation key as hidden, the model will not compile. And if you mark any other property as hidden, but reference it in a QueryInterceptor, an exception will be thrown.
I am not 100% sure if this is the case but, if you apply the “ScaffoldColumn(false)” attribute to the property that you want to hide it may work. Here is the MSDN entry for that attribute