I have a field (in the child record) that changes color based on the title in
the child record (e.g. Case(Title="Alumni President", GetRepetition(Colors,1),
Case(Title="Key Contact", Get Repetition(Colors,2)).

I place this calculation field behind the "Title" field (which is set to clear)
 in the portal  All works very, very beautifully(!) until the user scrolls
through the portal, upon which time all the title fields change to the
background color of the layout!

I can't figure out how to keep the color of the calculation field active behind
the title field while scrolling.  One suggestion might be to increase the size
of the portal so the user doesn't have to scroll, but that won't work - there
are simply too many portal items to make that practical.

I really like the color coding of titles - visually it is very appealing and
useful and so in the meantime I've simply decreased the color calculation field
in size to appear to the left of the title, but if anyone knows how I can make
the color appear behind the entire title field without it disappearing on
scrolling, I would be very happy!

Thanks

The only way to avoid this is to set the fields placed over the calc not
to allow entry.  If you want to be able to create or edit records through
the portal, this is impossible.  Instead of having the calc field behind
the records, have the calc field display different states of an icon
(faded/bright) and place it independently of the fields, formatted, with
invisible fill and border and not to allow entry.  This same icon can be
formatted as the button that goes to the related record.

If you would prefer to keep the background colour calc, there are work
arounds for editing and creating new related records:

1.  To edit existing records in the portal, format the calc field (which I
assume takes up the whole portal row) as a button which goes to the
related record then runs an external subscript in the related file that
goes to the form view layout.

2.  To create new records, create a button which sets a global field in
the related file to the match field value of the current record in the
master file, then runs an external subscript in the related file that goes
to form view, creates a new record and sets the related files match field
to the value in the global field.

Make sure that there is a button on the form view of the related file to
facilitate a speedy return to master file (Open script step will suffice).

--
Bridget Eley