Skip to main content
Question

Apps 10 Dev Studio

  • April 13, 2026
  • 1 reply
  • 6 views

Forum|alt.badge.img+10

Hi,

 

As a customer can we use Dev Studio on Apps 10 to create a custom projection which could then be called REST? We need an eTag which is why the Quick Report option is not suitable.


Thanks,

Matt

1 reply

Forum|alt.badge.img+9
  • Hero (Partner)
  • April 15, 2026

Hi,

 

As a customer can we use Dev Studio on Apps 10 to create a custom projection which could then be called REST? We need an eTag which is why the Quick Report option is not suitable.


Thanks,

Matt

Hi ​@Matthew ,

Short answer: not really in Apps 10.

Dev Studio in Apps 10 doesn’t support creating custom projections with full REST behavior (like you have in IFS Cloud). So you can’t build a custom projection and expect features like eTag / optimistic locking to work the same way.

You’re also correct that Quick Reports won’t work here—they don’t provide REST resource semantics like eTag.

What are your options?

  • Use a standard API / LU if available
    If the data exists in a standard object exposed via REST, that’s the best route since eTag handling is already built-in.
  • Custom logic + external service (most common workaround)
    If you must have eTag, typically customers:
    • implement logic in Apps 10 (PL/SQL / APIs)
    • expose it via a middleware or custom REST layer
    • handle eTag/concurrency there
  • Custom solution inside Apps 10
    Possible, but it won’t behave like a true projection and won’t natively support eTag.

Bottom line

Apps 10 isn’t designed for custom REST projections with eTag support—that capability really comes with the IFS Cloud projection framework.

If eTag is a strict requirement, you’ll likely need to handle it outside Apps 10 rather than trying to force it within Dev Studio.