gupta-aashika

> Does it make any difference if you add entity sets for `Location` and `Competitor` as well? So we don't want to introduce a separate entity for Location and Competitor...

Hi @julealgon, Thank you so much for answering. I tried adding [Key] attribute over CustomId in all the three entities. It creates the navigation source correctly. Is adding [Key] attribute...

@julealgon I verified the question #690. Our case is slightly different from what is mentioned there. Here, we are trying to expand and then select properties as per need. We...

> If you need to select a property from a relationship, you need to expand the relationship first. So you are not "selecting" competitors, you are "expanding" them. Here, why...

@julealgon I am able to get only the competitor in my response using the below request. But now I am looking to get only field1 in my response. Instead I...

> It's not clear to me what you mean by `field1` and `field2` @gupta-aashika , can you elaborate please? Sorry for the mismatch in entity model. field1 is loc1 and...

If I remove competitor selection, then, the response has all the fields present in mockOpenType. Example response: ``` { "@odata.context": "/$metadata#SomeType", "value": [ { "mockOpenType": { "customId": 8612, ##Other fields...

@xuzhg Thank you so much for listing out the important points. I went through the complete odata conventions here: http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part2-url-conventions/odata-v4.0-errata02-os-part2-url-conventions-complete.html#_Toc406398162 As per the document, for select, there are two simple...