A custom field originally added to one entity (like Customer Order) needs to also show up on a different, unrelated entity's page (like Business Opportunity) as a Projection Configuration — the custom field was added to the Entity Configuration and mapped, but it doesn't show up in the attribute list when trying to add it to the second page's content, even after refreshing the projection cache.

All FAQ questions / Platform, Aurena, and customization

Answer

This isn't a caching or setup mistake — it's a documented framework limitation: Custom Attributes connected to a Standard Entity aren't supported when configuring Projections (as opposed to Customizations, which have fuller custom-field support). If you need a custom field to genuinely appear across multiple unrelated standard entities' pages via Configuration, this specific combination isn't currently possible; you'd need to look at a Customization-based approach (through Developer Studio) instead if that cross-entity requirement is firm.

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

← Browse Platform, Aurena, and customization questions