Nick Ashcroft 10/13/2020 5:48:02 AM
yes - Im getting that now. Best thing i can think is to add a 'dummy' single ref 'State' to be used as a filter for the 'child' multi-ref City and then remove the dummy value on saving.
Taking the state/city example (both multi-ref), I add a 'single ref' to State as well as the multi-ref State. The 'city' multi-ref can be filtered based on the single ref 'state' filter using a 'Record Picker Match Conditions' condition.
The user can consider this like a 'state filter' to limit the list of cities when making their selection to reduce the risk of choosing a wrong city. However, it doesnt actually prevent disallowed combinations of multipe states and multiple cities.
TeamDesk support have also indicated a dependency between 2 multi-refs is sadly not possible. However, they gave a good tip to use a validation rule to block wrong combinations being added (using some lookups and formula eg 'Contains([Address_states],[City State])=False' but its a bit clunky because it doesnt tell you what the offending combination is - just a blocking error.
thanks for the feedback !