Bulk contacts import error when we have two groups with same name #6528

New Issue

adam · 2025-12-29T19:42:00+01:00

adam commented

2025-12-29 19:42:00 +01:00

Originally created by @3bruno on GitHub (Jun 1, 2022).

NetBox version

v.3.2.4

Python version

3.9

Steps to Reproduce

1 - Create two groups with same name (the group can be child from another group);
2 - Try to import a contact using this group created in step 1;
3 - Gives the following error: "Row 1 group: "Vendas" is not a unique value for this field; multiple objects were found".

Expected Behavior

For groups that have a parent, we should be able to import the contacts.

Observed Behavior

In Contact Bulk Import we do not have a parent group field then we receive the following error:
"Row 1 group: "Vendas" is not a unique value for this field; multiple objects were found"

Originally created by @3bruno on GitHub (Jun 1, 2022). ### NetBox version v.3.2.4 ### Python version 3.9 ### Steps to Reproduce 1 - Create two groups with same name (the group can be child from another group); 2 - Try to import a contact using this group created in step 1; 3 - Gives the following error: "Row 1 group: "Vendas" is not a unique value for this field; multiple objects were found". ![image](https://user-images.githubusercontent.com/72423012/171397085-a771eee2-2945-49b2-aa8b-74bf2f376fb2.png) ![image](https://user-images.githubusercontent.com/72423012/171396958-76f17387-afdc-4ac4-93d0-1e0da062b1da.png) ### Expected Behavior For groups that have a parent, we should be able to import the contacts. ### Observed Behavior In Contact Bulk Import we do not have a parent group field then we receive the following error: "Row 1 group: "Vendas" is not a unique value for this field; multiple objects were found"

adam added the type: bug label 2025-12-29 19:42:00 +01:00

adam closed this issue

2025-12-29 19:42:00 +01:00

adam commented

2025-12-29 19:42:01 +01:00

@jeremystretch commented on GitHub (Jul 19, 2022):

This isn't a bug, it's just a limitation of the import form: There's no way to reliably indicate a group by name because the name is not unique. Instead, you can specify group.pk as the column header and provide the group's database ID. This ensures that you're referencing the correct object.

@jeremystretch commented on GitHub (Jul 19, 2022): This isn't a bug, it's just a limitation of the import form: There's no way to reliably indicate a group by name because the name is not unique. Instead, you can specify `group.pk` as the column header and provide the group's database ID. This ensures that you're referencing the correct object.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#6528