starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Unable to assign contacts to either ASN or Tenant Group objects #11172

New Issue
Closed
opened 2025-12-29 21:41:18 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:41:18 +01:00
Owner
Copy Link

Originally created by @smiket9 on GitHub (May 14, 2025).

Deployment Type

NetBox Cloud

NetBox Version

4.2.0

Python Version

3.10

Steps to Reproduce

  1. Assign an existing contact via "Contact Assignment Bulk Import"
  2. Import a contact targeting either ASN or Tenant Group assignment, using object_type (tenancy.tenantgroup / ipam.asn), object_id, contact.id (using id to prevent duplication confusion), and role.

Expected Behavior

It is expected that contacts will be assigned to either a tenant group or ASN, like I managed to do using "Contact to Tenant" assignment.

Observed Behavior

Getting the below error (same error produced via the API attempt)

"Record 1: Contacts cannot be assigned to this object type (Tenancy | tenant group)."

Originally created by @smiket9 on GitHub (May 14, 2025). ### Deployment Type NetBox Cloud ### NetBox Version 4.2.0 ### Python Version 3.10 ### Steps to Reproduce 1. Assign an existing contact via "Contact Assignment Bulk Import" 2. Import a contact targeting either ASN or Tenant Group assignment, using object_type (tenancy.tenantgroup / ipam.asn), object_id, contact.id (using id to prevent duplication confusion), and role. ### Expected Behavior It is expected that contacts will be assigned to either a tenant group or ASN, like I managed to do using "Contact to Tenant" assignment. ### Observed Behavior Getting the below error (same error produced via the API attempt) "Record 1: Contacts cannot be assigned to this object type (Tenancy | tenant group)."
adam added the netbox label 2025-12-29 21:41:18 +01:00
adam closed this issue 2025-12-29 21:41:18 +01:00
adam commented 2025-12-29 21:41:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 14, 2025):

As the error message indicates, these types of objects do not support contact assignment. Please submit a feature request if you'd like to propose adding contact support for these.

@jeremystretch commented on GitHub (May 14, 2025): As the error message indicates, these types of objects do not support contact assignment. Please submit a feature request if you'd like to propose adding contact support for these.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label netbox
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11172
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?