[ 
https://issues.apache.org/jira/browse/OLINGO-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718877#comment-16718877
 ] 

Archana Rai commented on OLINGO-1307:
-------------------------------------

Hi Peter,

I still can't simulate this issue.

I tried with 
ESCompMixPrimCollComp(1)?$expand=PropertyMixedPrimCollComp/NavPropertyETTwoKeyNavOne($select=PInt16,PropertyString)
 from Olingo technical service and this works fine:

{
 "PropertyInt16": 1,...
 "PropertyMixedPrimCollComp": {
 "PropertyInt16": 1,...
"NavPropertyETTwoKeyNavOne": {
 "PInt16": 1,
 "PropertyString": "2"
 }}}

 

The metadata is something like this:
<ComplexType Name="CTMixPrimCollComp">
<Property Name="PropertyInt16" Type="Edm.Int16"/>
 ...
<NavigationProperty Name="NavPropertyETTwoKeyNavOne" 
Type="Namespace1_Alias.ETTwoKeyNav"/>
<NavigationProperty Name="NavPropertyETTwoKeyNavMany" 
Type="Collection(Namespace1_Alias.ETTwoKeyNav)"/>
</ComplexType>
 
<EntityType Name="ETCompMixPrimCollComp">
<Key>
<PropertyRef Name="PropertyInt16"/>
</Key>
<Property Name="PropertyInt16" Type="Edm.Int16" Nullable="false"/>
<Property Name="PropertyMixedPrimCollComp" 
Type="Namespace1_Alias.CTMixPrimCollComp"/>
</EntityType>
Please help me simulating the issue.
 
Thanks,
Archana

> OData V4 requests for property and navigationproperty values of complexTypes 
> that are not included in the selected items are ignored
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OLINGO-1307
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1307
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-server
>    Affects Versions: (Java) V4 4.4.0
>            Reporter: Peter Lawrence
>            Priority: Blocker
>             Fix For: (Java) V4 4.6.0
>
>
> *URL Request*
> Unsuccessful:
> {code:java}
> Employee('NWD~ContractEmployee-1')?$expand=employer/contractEmployer($select=label,subjectId){code}
> Successful:
> {code:java}
> Employee('NWD~ContractEmployee-1')?$select=employer&$expand=employer/contractEmployer($select=label,subjectId){code}
> *Steps to reproduce the problem:*
>  The OData model contains a complexType, with navigationProperties as values:
> {code:java}
>  <EntityType Name="Employee" OpenType="true">
>   <Key>
>     <PropertyRef Name="subjectId"/>
>   </Key>
>   <Property Name="subjectId" Type="Edm.String" Nullable="false"/>
>   ...
>   <Property Name="employer" Type="northwind.employer"/>
>   ...
>  </EntityType>
> <ComplexType Name="employer">
>  <NavigationProperty Name="contractEmployer" 
> Type="Collection(northwind.Shipper)"/>
>  <NavigationProperty Name="parttimeEmployer" 
> Type="Collection(northwind.Supplier)"/>
>  </ComplexType>
> {code}
>  
> *Other information*
> This was raised originally with the OpenUI5 project as it was thought that 
> the $select should have been included in the request. However they have 
> responded saying it is indeed not necessary according to the standard: 
> [https://github.com/SAP/openui5/issues/2235#issuecomment-428106366])



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to