A mandatory field (e.g. Discount % on Supplier for Purchase Part) always defaults to 0 the moment a new record is started, which defeats the point of it being mandatory since it's never actually empty for the user to notice. Can the default value itself be suppressed so users are forced to enter a real value?

All FAQ questions / Procurement and buying

Answer

Yes — set up a Process Enrichment workflow that listens to the entity's own …_Default() projection action (for example PurchasePartSupplier_Default() on SupplierForPurchasePartHandling) with After timing, and have the workflow set the Discount value to null in that response. This works by changing what the API returns for default-value population in the UI, rather than intercepting or blocking the actual create call — the field stays genuinely mandatory, but nothing pre-fills it with 0, so users have to enter a real value themselves.

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

← Browse Procurement and buying questions