Hi all:

I'm sure this has been covered but maybe my search criteria is lacking.

I used a couple of AI engines and seem to get contradictory advice, so here I am. Referring to the image below of a portal, I have it set (in the portal, not the relationship) to sort on Documents Required (has a pop-up menu attached). The problem is, after creating (or while editing) a new portal record, when a user chooses a value in Documents Required then the sort of (naturally) shifts, but I don't want it to shift while they're editing that record until a date is entered into the "When?" field or when they leave the portal altogether. How do I pull that off?

Cheers,

Rich

I don't think you are describing the problem accurately.

A portal will not resort until you commit records. Not even if you exit the portal to go to a field of the parent record. If you see a shift in the record's position then a commit has occurred, either by the user or possibly by a script trigger.

You could probably prevent premature committing by the user by validating the When? field as not empty. My preference would be to bypass the issue by scripting the process of creating (and possibly editing too) a child record in a card window.

Edited Friday at 03:11 PM5 days by comment

Sounds like a plan. Thanks!