Philmodjunk made a note on this error a while ago here:
Unstored calculations and global fields cannot be used on the Many side of a relationship as they cannot specifically match to any one record. A stored calculation should update correctly for you without it needing to be unstored. Just don't use a data field with an auto-entered calculation here unless you have no other alternative as that won't update automatically.
What types of fields are used in "_uc_1 = complete_boolean"?
Are they both number fields?
Is a value auto-entered into either?
The _uc_1 field is an unstored calculation, which was the problem.
I guess my question is how does the portal use the relationship while a find cannot? because the portal is working fine.
1 of 1 people found this helpful
A find between a Parent record and a child record in the child record's field where the parent records key is an unstored calculation or global.
It doesn't work because the FIND is from the context of the Parent, which means from the child record the relationship is used to Find the associated Parents. However, since the relationship is invalid, due to the parents key being unstored, the Child cannot relate back to the parent. Its basically a one-way relationship.
The portal works because its only relating from the parent to the child. A find must be valid both ways to 'Find' the parents.
That makes total sense. Its where you are performing the find that matters, why didn't I think of that?!
I guess the reason I got confused is because the portal is on the parent record layout. Seems obvious now!
Thanks for that clarification