is your calculated text field stored ?
You can use a non-stored field in a relationship, but only on the left side of the relationship, since the filter effect of the relationship predicate works via an index on the right side fields.
But you say ...
I am dynamically filtering records in a portal by payment status using a filtered relationship
.. and don't tell us if the break occurs with a change in the relationship setup or the portal filter.
Thank you erolst.
It is unstirred but on the right side.
The break is in the relationship.
1 of 1 people found this helpful
I assume - for what it's worth - that cPaymentStatus compares an invoice amount with the sum of related records in a Payments table, and so can inherently not be stored.
You could create a "regular" text field for the payment status and use a script that updates it whenever a payment is registered (or deleted or modified, if your business rules allow it).
You can use the formula from the calculation field for a Set Field step in the script, if you execute that step from the same context.
This field can be stored and used as a match field.
Yes I was doing that and it works fine. I was trying to eliminate a redundancy.