Default value for a custom field (when the field is not added)

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