Creating a new custom-list page bound to a Custom Logical Unit fails when the page tries to populate, with an OData error like 'ONLY_FOR_TYPED_PARTS: $select is only allowed for typed parts' or 'NAMESPACE_NOT_ALLOWED_AT_FIRST_ELEMENT' — the same basic steps (custom entity, custom projection, new page, List element bound to the entity) worked before for a similar simple custom list.

All FAQ questions / Platform, Aurena, and customization

Answer

Check that the list's Datasource Entity Set field on the page is actually populated — leaving it empty is what produces these exact OData errors when the page tries to load data, since the client doesn't have a valid entity set to query against. Setting the Datasource Entity Set explicitly to the entity set you want the list to pull from resolves both of these error messages.

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