A custom field's Default Value, set via a PL/SQL Expression that calls another custom field's own generated Get_ function with a runtime parameter (like the current record's contract/catalog number), throws an 'invalid identifier' error — is passing parameters into a PL/SQL Expression default value supported?

All FAQ questions / Platform, Aurena, and customization

Answer

No — a custom field's Default Value PL/SQL Expression doesn't support passing parameters into the function it calls; this is a confirmed platform limitation, not a syntax mistake in how the parameters were written. A Default Value PL/SQL Expression needs to be a parameterless call or a fixed expression, rather than something that takes the current record's own field values (like contract or catalog number) as runtime arguments.

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