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

Group is required attribute on Contact object when using REST API #5626

New Issue
Closed
opened 2025-12-29 19:30:16 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:30:16 +01:00
Owner
Copy Link

Originally created by @rodvand on GitHub (Nov 7, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.1-beta1

Python version

3.8

Steps to Reproduce

curl -X POST \
-H "Authorization: Token TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json; indent=4" \
https://NETBOX/api/tenancy/contacts/ \
--data '{
    "name": "Martin"
}'

Expected Behavior

Contact is created.

Observed Behavior

{
    "group": [
        "This field is required."
    ]
}

In the API docs the group attribute is set as required, while it is not (at least visibly) required in the NetBox UI.

Adding "group": null to the curl command allows the contact to be created.

Originally created by @rodvand on GitHub (Nov 7, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.1-beta1 ### Python version 3.8 ### Steps to Reproduce ``` curl -X POST \ -H "Authorization: Token TOKEN" \ -H "Content-Type: application/json" \ -H "Accept: application/json; indent=4" \ https://NETBOX/api/tenancy/contacts/ \ --data '{ "name": "Martin" }' ``` ### Expected Behavior Contact is created. ### Observed Behavior ``` { "group": [ "This field is required." ] } ``` In the API docs the group attribute is set as required, while it is not (at least visibly) required in the NetBox UI. Adding `"group": null` to the curl command allows the contact to be created.
adam added the type: bugstatus: acceptedbeta labels 2025-12-29 19:30:16 +01:00
adam closed this issue 2025-12-29 19:30:16 +01:00
adam commented 2025-12-29 19:30:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 8, 2021):

For anyone interested, this is a peculiar quirk of uniqueness validation within DRF. Because the group field is part of a uniqueness constraint, the serializer field must have a value for it (even if that value is null).

@jeremystretch commented on GitHub (Nov 8, 2021): For anyone interested, this is a peculiar quirk of uniqueness validation within DRF. Because the `group` field is part of a uniqueness constraint, the serializer field _must_ have a value for it (even if that value is null).
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 beta status: accepted type: bug
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#5626
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?