I have an unstored calculation field that is concatenating several other fields together from related tables. I'm trying to set up conditional formatting to highlight this cell when the calculated result is a duplicate of an already-existing record. I've done some research and tried self-joins, but I suspect the "unstirred" part of the calculation might be tripping me up (I can't select any other storage option because it's using related tables).
Any suggestions? Thank you for any help.
Can you change your calculation to an auto-enter calculation. This would solve your storage issue. However, it might introduce update issues if one of the related values is changed. Otherwise, you might be able to use ExecuteSQL to check for duplicates as it runs outside the relational engine.