Ghost highlight in null portal row

[Jason Tempestini]

I'm using a system to highlight a portal row by using a calc field which picks up a chip from a repeating container field. The calc result, clearly, is container.

The individual rows pickup their "highlight" chip just fine, but the open last row of the portal (this portal allows record creation) also picks up the highlight chip.

How can this be? There's no data for it to link to. How can the nonexistant calculating container field pickup data from an unrelated (no key fields filled) table?

Please help.

[IdealData]

Are you sure that the fields in the portal rows actually belong to the relationship?

[Jason Tempestini]

Yeah. The field in the portal does belong to the relationship. The issue was that the "non-record" or last field in the portal was connecting to whatever the selected record was connecting to.

We came up with two solutions: 1. We can make the relationship not allow creation of records. That isn't how we want it to work, but you can script around that.

2. (the solution we took) We used the script (row selector) to make a connection to a related table (same file) which included our custom "highlight" chip. Previously this chip had been kept in a global field in the same table. When we made the relink, it worked, but only if we do a flush joined cache screen refresh each time we change.

[comment]

Perhaps if you provide your script and the calculation (or attach your file)...