Skip to main content

Hello Community,

I have a question regarding the behavior of default values in IFS custom fields. I have created a new custom field and set its default value to True in IFS Apps 10 (Version 15). This works as expected when users have added the field to their screen via the column chooser.

However, for users who have not added the field to their screen, the value appears to be null when a new line is added.

Is there something I might have missed in the configuration? Or could you suggest a way to ensure that the default value is applied for all new entries, regardless of whether the field is visible on the screen?

Appreciate your help!

Regards.
Aravinda

 

Hi,

This may be due to that default value set when you press + button in client .May be you can  create a custom event to set value if its null though its an additional work?

 

Best Regards,

Wasana

Hello ​@wahelk,

Thank you for your response.

The intended behavior of this custom field is to help identify the source of newly added lines — specifically, to distinguish between entries created via IEE and those coming from Aurena (Tech Portal).

Our goal is:

  • When a new line is created via IEE, the custom field should be automatically populated with a predefined value (TRUE in this case)

  • When a line is added through Aurena, the field should remain null.

However, using a custom event to set the value causes it to populate regardless of the source — meaning the event triggers for both IEE and Aurena, which is not the desired outcome.

In testing, I noticed that when the custom field is added to the user’s screen, it behaves as expected — the value is correctly populated when a line is created from IEE. But if the field is not visible on the screen, it remains null, even if the line was created in IEE.

If you have any recommendations or best practices for handling this kind of differentiation, I'd really appreciate your insights.

 

Best Regards.
Aravinda

If I understand correctly, now you want to know if the PL/SQL code (custom event) is called from IEE or Aurena. If so, this post might be useful:

 

Reply


Terms & ConditionsCookie settings