Even you use the connection object, itβs just a view, it refers (searches) for another record: when you create a record on the connection object, you still have to configure each search individually, and you still only create one record.
Master Detail relationships are essentially a search for steroids, one object becomes a descendant of another and will be deleted, if the parent object is deleted, they will not provide an interface for searching many records at once.
If you're not a developer, then it's best for you to either create a record of the connection object, or look at using dataloader. You can prepare your data in Excel or similar, and then upload all the records to Salesforce in one go.
If you are a developer or have developers at your disposal, then what we have done in the past is to create a Visualforce page to complete this task. For example, if you want to associate a bunch of contacts with an account, we will have one search box for the account on the page, and then several search fields related to the contact fields. Using a SOQL query, you can find all the contacts matching the search parameters and display them in a list where you can provide flags to allow the user to select the contacts they need. Then this is just a case of iterating over selected contacts by setting up their account for them.
There are areas in Salesforce (such as the email sending feature that you mentioned) where you can clearly see that a specific job has been done to complete a specific task - another instance of what you want is in an area where you can manage your members campaign. This is a model that I copied in the past when implementing a Visualforce page, as described.
Good luck
source share