Hello,
We are trying to develop a projection customization which will eliminate the need of sending multiple calls to InventoryPartService to fetch Inventory Part Information and their Characteristics. Currently, InventoryPartService has the projection action GetPartInformation which does this for us. However, we also require the ability to filter on specific attributes both in the top level and in the nested structure for the characteristics. Using OData functions such as $filter, $top, $select, etc is not possible when calling projection actions.
My question is, is there any way to create a customized entity or customize the projection in a way such that when sending a GET for the InventoryPart entity, it would return the header information along with the Characteristics in one structure? This would of course be a nested structure where InventoryPart is the root, and then Characteristics would be a list attribute for all of that part’s characteristics.
I know standard IFS code generation for arrays like this typically creates a separate endpoint. So when a GET is sent for InventoryPart it would return the part information. Then a separate request would be required to fetch the characteristics so:
- GET InventoryPartService.svc/InventoryPartSet (here we can use $filter)
- GET InventoryPartService.svc/InventoryPartSet(Contract='{Contract}',PartNo='{PartNo}')/Characteristics (here we can also use $filter)
But we want to combine the responses of these two such that GET InventoryPartService.svc/InventoryPartSet returns both header and characteristic information, and we can also use OData functions. Does anyone know of a way of doing this?
Thanks!