Can a custom/add-on component's client file use a standard projection that technically belongs to a different core component (e.g. an add-on client referencing CustomerOrderHandling, which belongs to the Order component)? Is that technically restricted?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Yes, it's allowed — there's no technical restriction preventing a client file in one component from using a projection owned by a different component. The real-world implication is a static dependency: your add-on component ends up depending on the projection's owning component, so both components need to be enabled, and a customer would need both installed/licensed together for the add-on to function — it's a licensing/deployment consideration, not a technical blocker.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions