Environment: IFS Cloud 25R2. Everything below is pure configuration (no IFS Developer Studio).
I have a multi-select custom enumeration field on a 1-to-1 custom LU, surfaced on the standard CrmCustomer page, and it will not SAVE.
Setup:
- Custom LU "CustomerClassClass" (1-1 with the customer, keyed by CUSTOMER_ID) with a multi-select custom enum field "Cf_Market_Classification".
- Added to the standard CrmCustomer page via Custom Projection Configuration on CrmCustomerHandling: the LU is added as a config entity plus a custom association (CrmCustomer to CustomerClassClass, key CUSTOMER_ID = Cf_Customer_Id), with CREATE/UPDATE/DELETE allowed.
- Displayed in a GROUP on a tab.
Symptom: editing the multi-select and saving fails with HTTP 400: "Malformed Request. Client Warnings are not supported for CREATE, UPDATE, DELETE operations in [CustomerClassClass] entity. So X-IFS-Accept-Warnings request header cannot be set to true." The failing request is the collection-element PATCH: Customers('X')/CrmCustomerBaseClass(Objkey='...').
What I have verified (via direct authorized OData calls in the same session):
- PATCH to the LU's OWN entity set (CustomerClassClassSet) WITHOUT the X-IFS-Accept-Warnings header returns 200 and saves fine.
- The SAME PATCH WITH the header returns the identical 400. This happens on BOTH the association path AND the own-set path. So the rejection is ENTITY-level (the custom LU's generated projection has no supportwarnings), not path-specific. The Aurena client attaches X-IFS-Accept-Warnings: true on CUD because the standard page's context supports warnings, and the config-added custom LU cannot accept it.
What I have tried:
- A Page Designer Singleton (singleton bound to the association; group bound to the singleton with empty property). The client still sends the header, still 400.
Questions:
1. Is there any CONFIGURATION-ONLY way (Custom Projection Configuration, a custom field/entity setting, or client/page config) to make the config-added custom LU entity advertise supportwarnings (accept the header), OR to stop the Aurena client from sending X-IFS-Accept-Warnings for that entity/command, so a multi-select enum in a group can save inline on the standard page?
2. Would presenting the multi-select via a LIST (instead of a group/singleton) change the CUD request shape and avoid the header?
3. If neither is possible in configuration: is the recommended pattern to edit the custom LU on a separate page/dialog bound to the LU's OWN projection (where the client omits the header)? And is a -Cust .projection with supportwarnings = [true] genuinely the only way to keep it editable INLINE on the standard page?
Thanks!
Our constraints and the ask (important): We are a configuration-only shop and cannot use IFS Developer Studio, so a -Cust .projection / Marble change is not an option for us. Surfacing a custom LU field and editing it inline on a standard page is a common, reasonable configuration scenario. If the ONLY way to make a config-added custom LU savable inline is a -Cust projection (supportwarnings), then "editable custom LU on a standard page" is effectively impossible with configuration alone - which feels like a product limitation / gap rather than a mistake on our side. Reasonable ask: allow Custom Projection Configuration (or a custom field/entity setting) to opt a config-added custom LU entity into supportwarnings, OR have the Aurena client omit the X-IFS-Accept-Warnings header for entities that do not support warnings, so custom LUs can be saved with pure configuration. Is there a supported config workaround today - and if not, can IFS consider closing this gap?
