Inconsistency in ContactAssociation uniqueness constraints

[jdueitt]

Environment

• Nautobot version (Docker tag too if applicable): 2.2.2
• Python version: 3.10.12
• Database platform, version: postgres, 16.2
• Middleware(s):

Performing a Import Objects job on the content type of extras | contact association does not honor the same uniqueness constraints as using the form to manually enter a new association. Specifically, associated the same contact, and role to multiple objects will result in a failure using the Job, but can be done manually by going to each object and assigning the contact.

Test Data

Location Types

name
Root Location

Locations

location_type__name,name,status__name
Root Location,Location 1,Active
Root Location,Location 2,Active

Contacts

name,email
Bob,bob@example.com

Steps to Reproduce

1. Create a CSV that associates the same contact, and role to two different objects of the same type (this requires knowing the ids of the generated locations when loading our test data, so this will change for everybody going through these steps

associated_object_id,associated_object_type,status__name,role__name,contact__name
7939407e-0dba-430b-bf54-b8d3e88258dc,dcim.location,Active,On Site,Bob
969beaa9-f75a-4b11-b6ae-15d6357cf5fe,dcim.location,Active,On Site,Bob

2. Utilize the import objects job to import the contact associations
   

Expected Behavior

The expected behavior is the form indicating that it successfully imported the contact associations.

Observed Behavior

[jdueitt]

I will be submitting a PR shortly that fixes this issue.

[jdueitt]

@glennmatthews the PR is now in for this. From my perspective, I have this resolved and it's not a hot button issue for me. So, no need to rush a new release out to get this rolled in.