1 of 1 people found this helpful
I'm not sure whether it will work the way you trying. But a different way to do it could be to have a boolean field on Employee that is marked as True whenever on the creation of the relationship between employee & CostCentre (using a business rule). That way your constraint should be as easy as 'BooleanField' = True'.
I agree with Ross's suggestion; add a boolean and also a rule to update the new field.
As for the duplicate values - depending on the number of employees in your table, you may be seeing duplicates because the display field is DisplayName and there are likely to be duplicate first and last name combinations (such as Mike Jones). You can test this theory by looking up one of the duplicates, noting the email or loginID, and then change the display field to email or loginID. Compare your results to determine if you're still getting duplicate values or if they just appear to be duplicate values but are actually referencing different employees.
~ Steve G