Skip to main content
Solved

Get Complex structures in ODATA, second question

  • January 11, 2023
  • 3 replies
  • 329 views
LevFredrB
Sidekick (Partner)
Forum|alt.badge.img+4

I earlier added the question https://community.ifs.com/topic/show?tid=30227&fid=50 regarding complex ODATA responses. 

Now, I just want someone to confirm the assumed framework limitation, or if it is no limitation. Just, to clearify things for me ðŸ˜€

According to ODATA standard the Expand feature is used to get/filter complex structures, like 1..m or m..1 or just 1...1 relations.

If you trying the Odata org example service, you can run the following request:

https://services.odata.org/V4/TripPinServiceRW/People?$expand=Trips($filter=startswith(Name, 'Trip'))

It will list the persons and the trips they have done. This will return a typical 1..m structure.

As I understand, there is no support for this Expand usage within Marble? Please correct me if I am wrong. The only usage of the Expand in Marble is references, i.e. 1..1, which means that below collection is not possible to achieve.

If this is a current limitation in Marble, will this feature be added in the future? (So the Expand can be used as it supposed to be used).

 

 

Best answer by Rifki Razick

Hi @LevFredrB ,

 

This particular $expand scenario (1 to many) is currently not supported in the IFS OData implementation. However we have plans to support this in a future release.

Also note that this can be modeled today in Marble using the array keyword in the projection model. But the current OData API implementation only provides the child items via a navigation per parent object.

e.g. Orders(Id=1)/OrderItems

 

Regards,

/Rifki

 

View original
Did this topic help you find an answer to your question?

3 replies

Rifki Razick
Hero (Employee)
Forum|alt.badge.img+9
  • Rifki Razick
  • Hero (Employee)
  • 72 replies
  • Answer
  • January 13, 2023

Hi @LevFredrB ,

 

This particular $expand scenario (1 to many) is currently not supported in the IFS OData implementation. However we have plans to support this in a future release.

Also note that this can be modeled today in Marble using the array keyword in the projection model. But the current OData API implementation only provides the child items via a navigation per parent object.

e.g. Orders(Id=1)/OrderItems

 

Regards,

/Rifki

 

Rifki
Jonas Feigl
1 person likes this
  • Jonas Feigl
    Jonas Feigl
Jonas Feigl
Superhero (Employee)
Forum|alt.badge.img+20
  • Jonas Feigl
  • Superhero (Employee)
  • 262 replies
  • January 13, 2023

@LevFredrB As Rifki has mentioned you cannot achieve this with the current IFS Implementation of the $expand functionality and this is a known limitation. If you build your own projection though (i.e. model it in Developer Studio) you can define structures including arrays though but the difference is that you will have to write the logic to fill these structures yourself in PL/SQL rather than having the fetching of the data being automatically implemented from the model as a SQL statement.

Rifki Razick
LevFredrB
2 people like this
  • Rifki Razick
    Rifki Razick
  • LevFredrB
    LevFredrB
LevFredrB
Sidekick (Partner)
Forum|alt.badge.img+4
  • LevFredrB
  • Author
  • Sidekick (Partner)
  • 9 replies
  • January 13, 2023

Thanks for the replys, yes. I have used the more manually way of to achieve the complex structure, by filling structures/arrays. It works but of course, even though the 1..m usage is not needed for the Aurena FW, it really usable for integrations. So, it would be create if the $Expand 1..m feature would be added to IFS OData logic (so it was possible to model in Marble too) 😀

 

Rifki Razick
1 person likes this
  • Rifki Razick
    Rifki Razick

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings