David Yack

So if you just specify 1 column it works, but as you get larger numbers it fails? Are you able to get an http trace to see what your get...

Currently we aren't supporting the If-Match yet on a Get to support checking for a change - I assume that is what you are after? Can we change the title...

Yes, right now I don't believe there a way we can encounter a 304 until we expose a way to do conditional retrievals - So agree when we add logic...

That is a good question I've not seen anything one way or the other - have you seen something that would indicate that would also return a 304, seems like...

Yeah I agree the web resources or any JS file etc will be impacted, but have you seen this on a Web API get request? Thx Dave

ok, will research a little more- either way should add 304 when we add conditional, just want to understand if there are other scenarios that will return it that need...

Are you suggesting we build something similar to crmsvcutil?

Not opposed to adding to CRMWebAPIConfig - we don't plan to add more constructor params

Agree this is painful the way OData works - similar occurs with Formatted values - Are you suggesting aliasfullname or adding an object alias with property of fullname. Either way...

That is not account.contact it's account["contact.fullname"] the property is the alias plus the field So you could do something like var myAccount = account as IDictionary; Console.WriteLine(myAccount["contact.fullname"]);