Greets, all:

I have a portal where I want to highlight the text field in it (in the first row) if a user fails to select a value for it; it would de-highlight after at least one value is chosen.

I tried using not IsValid ( EVENT_PRESENTER::_kflt_Event_ParentID ) as a calculation, and it sorta works: the field de-highlights after the first portal row field has a value, but still highlights the empty waiting/next portal row field beneath it.

Since the portal row isn't active (because I don't want to force the user to go to the field/portal row every time the record is loaded), I don't think a calc based on the active portal row will work...but I could be wrong.

Any ideas? TIA for your help!

Figured it out: I created a calculation field (GetFoundCount) in the child table; I changed the Conditional Formatting field calc to:

Case ( ( EVENT_PRESENTER::zz_GetFoundCount__lcn ) = 0 ; 1 ; 0 )

So, if there are no related records then that results in a False in the Conditional Formatting calc, so no fill/highlighting; at least one record, a result of True.

*pats himself on the back* 

Edited July 13, 20223 yr by WF7A
Typo

I would think you want to do:

IsEmpty ( Self ) and not IsEmpty ( YourPortalTable::PrimaryKey )

provided that the PrimaryKey field auto-enters a value on creation, not on commit.

Can't see how the number of related records is relevant here. Do you not want to highlight the empty field in the 2nd or 3rd portal row, when a 2nd or 3rd record is added without filling that field?

 

Thanks. For the primary key in all the tables here, it's auto-entered with a calculated value of Get ( UUID ), so keys aren't auto-entered serial numbers (...so no commit/on creation radio buttons available. )

No, no highlighting is needed after the first row is populated since the conditional formatting is just an indicator to remind users to populate the field/portal with at least one value; more than one is just gravy.