Hello,

I have just consulted the following IFS file, linked to the 25R1 version :

25R1 Fixes for Customer Reported Issues.xlsx

I found that for one of my cases “CS0332557” the release note is as follows:

The CustomerOrderInvHeadEntity.svc and CustomerOrderInvItemEntity.svc entity services were previously unable to expose certain attributes such as Customer Address Name and Debit Invoice ID due to limitations in the overtaken base views. To ensure full attribute availability, customers are now advised to use the projection service CustomerOrderInvoiceHandling.svc, which exposes the relevant data through the CustomerOrderInvHeadSet projection. As part of ongoing improvements, the usage of the CustomerOrderInvHeadEntity.svc entity service is planned to be phased out in future releases.

Until now, IFS teams have always recommended us to use Entity APIs rather than Handling APIs, and this comment seems to reverse the trend.

FYI We've already encountered multiple “Entity” APIs that were unstable (and opened several cases).

For some developments, we chose to use only Handling APIs (for reasons of ease of use), but for most interface developments, we used Entity APIs.

Is there a risk that other Entity APIs will disappear? Is the IFS recommendation to use them as a priority still valid?