Reminder! Until the end of the month, our Learning Track over Advanced Normalization is unlocked and available to all Grooper xChange users!
Grooper 2.80.0043 is now available! Check the  Downloads Discussion for the release notes and to get the latest version.
Grooper 2.90.0051 is now available! Check the  Downloads Discussion  for the release notes and to get the latest version.

Why do Hidden Fields not fire their expressions?

BradleyBradley Posts: 91 ✭✭✭
edited October 2018 in The Astronauts (Q&A)
I have a hidden field that is used as a utility for mapping a specific unique value at Document Export. The Calculate Expression does not execute if the field isn't visible. This causes the document export to fail.

The only way to currently fix this for production is to show that utility field.


  • rmccutcheonrmccutcheon Posts: 756 mod
    This has been reported
  • dlittledlittle Posts: 39 ✭✭✭

    This is not a bug.

    Field validation is not performed on hidden fields by design. Field validation is the action that triggers the execution of Field Expressions (with the exception of the Default Value Expression).

    Validation is not performed, because if a field is hidden, and invalid, there will be no way for a user to correct the field issue.

    Can you elaborate on what you mean by a 'specific unique value'? There may be alternative functionality that can accommodate what you're trying to accomplish.

Sign In or Register to comment.