9

I am building out my new v4 service and all was going well until I added a new controller for a new model/entity and got this error when starting the site up for a test run.

The controller seems to be correctly coded, just like the others.

The path template 'Customers' on the action 'GetFeed' in controller 'CustomersOData' is not a valid OData path template. Resource not found for the segment 'Customers'.

What on Earth does that mean?

abatishchev
  • 98,240
  • 88
  • 296
  • 433
Luke Puplett
  • 42,091
  • 47
  • 181
  • 266

2 Answers2

4

This error happens in Web API attribute routing scenario. Web API attribute routing will check all ODataRouteAttributes for all found ODataControllers when running the initializer of HttpConfiguration.

You mentioned that the error happened after you added a new Model/entity, so I guess you maybe have two Edm Models:

ModelA, ModelB

And EntitySet "Customers" is only in one of the model, for example the ModelA.

Besides, you may have the following codes for the new added Model:

config.MapODataServiceRoute("...", "...", ModelB);

When start-up, Web API finds the attribute:

[ODataRoute("Customers")]
public IHttpActionResult Get()
{
 ...
}

but, Web API can't find the "Customers" entity set in ModelB.

I think you can fix it by putting all into one model.

Sam Xu
  • 3,264
  • 1
  • 12
  • 17
  • It was a Q/A so I answered also. I only have a single model for this OData v4, but your diagnosis was correct. The term "model" is confusing since it can refer to a model class (entity) or an EDM (entity data model). I think case, I'd add a new entity model class and controller but forgot to register the entity set with the OData model builder (the OData EDM is separate to the EF EDM at present, by design). – Luke Puplett Jan 09 '15 at 17:58
  • No offence, but I'm ticking my own answer since its simpler, accurate and contains the code that fixes the issue. I am grateful for your answer though. – Luke Puplett Jan 09 '15 at 17:59
  • Sam, is it possible to define a secondary edm model and *not* include some of the OData APIs in the secondary model, *on purpose*? I'm having a similar issue as above, see my question: https://stackoverflow.com/questions/51314002/expose-only-a-subset-of-net-odata-apis-for-a-route-return-404-for-excluded-api – James Wierzba Jul 23 '18 at 22:46
3

If this is happening on start-up then check that you have added your Customers model type to the model builder during start-up.

builder.EntitySet<CustomerModel>("Customers");

It sounds like the attribute mappings are being enumerated for the new controller but it cannot map the Customer model type back to an entity set.

Note: Q/A I figured this out almost immediately but I'm posting here because I'll probably do this again and forget what I did wrong!

Luke Puplett
  • 42,091
  • 47
  • 181
  • 266