Admittedly, something I've run into simply out of user error– sometimes in testing... sometimes not :(



When writing a rule with the Action 'Load to Relationship', the action acts as an upsert. Because the 'Relationship Type' dropdown defaults to the first type alphabetically, if you forget to select the type you're wanting to configure the action for, the action will create Relationships for all records in the dataset from 'Setup Action'.



Ex:

1. I create a dataset for relationships of Relationship Type "B"

2. In the actions, I accidentally leave the config to Load to Relationship Type "A"

3. Result: all of the records from the dataset will get newly created relationships of Type "A" when all I wanted to do was update records of Type "B"



Ideas:

1. Allow for Operation selection (Insert, Update, Upsert)– similar to other "Load to" actions. This way, if all I want to do is update fields, new relationships won't be created. 

2. Default the Relationship Type selection to blank– this way an error prompt will remind admins to make a correct selection. 



Question:

Is there an easy way to update relationships of any type without needed to create new actions for each relationship type?



Ex: I have a custom relationship field for "Relationship Status". I want to have a rule set Relationship Status to "Churn" if the Account has churned. To do so now, I have to fetch churned Accounts with "Active" Relationships, and then setup a separate Load to Relationship action for each of the relationship types. This is the same for any rule that I want to write that updates fields on relationships.