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

Error while editing the existing device. #5118

New Issue
Closed
opened 2025-12-29 19:24:27 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:24:27 +01:00
Owner
Copy Link

Originally created by @Narek307 on GitHub (Jul 29, 2021).

NetBox version

v2.11.8

Python version

3.6

Steps to Reproduce

  1. Edit Device
  2. Edit any field
  3. Click on update

Expected Behavior

Device has been edited.

Observed Behavior

Hello,
I am getting the following error: "Unknown field name 'coordinates' in custom field data." while editing the existing device.
Can you please help me to solve this issue?
Capture

Below mentioned Workarounds have been tested already.
Workaround 1: create a new custom field called "coordinates" for Device; and then delete it. That should clean up your data. (However it's unclear how it got into this state in the first place)
Workaround 2: fix up the custom_field_data field in dcim.devices using a Django script or direct SQL update

Originally created by @Narek307 on GitHub (Jul 29, 2021). ### NetBox version v2.11.8 ### Python version 3.6 ### Steps to Reproduce 1. Edit Device 2. Edit any field 3. Click on update ### Expected Behavior Device has been edited. ### Observed Behavior Hello, I am getting the following error: "Unknown field name 'coordinates' in custom field data." while editing the existing device. Can you please help me to solve this issue? ![Capture](https://user-images.githubusercontent.com/53900129/127483013-30daccc5-d3c1-4dcc-aaf1-42b0131c0c98.PNG) Below mentioned Workarounds have been tested already. Workaround 1: create a new custom field called "coordinates" for Device; and then delete it. That should clean up your data. (However it's unclear how it got into this state in the first place) Workaround 2: fix up the custom_field_data field in dcim.devices using a Django script or direct SQL update
adam added the type: bugstatus: revisions needed labels 2025-12-29 19:24:27 +01:00
adam closed this issue 2025-12-29 19:24:27 +01:00
adam commented 2025-12-29 19:24:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 29, 2021):

Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v2.11.10. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.

@jeremystretch commented on GitHub (Jul 29, 2021): Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v2.11.10. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.
adam commented 2025-12-29 19:24:28 +01:00
Author
Owner
Copy Link

@Narek307 commented on GitHub (Jul 29, 2021):

Sorry, that was my bad. It was related to netbox_topology_view plugin activation. The problem has been solved.

@Narek307 commented on GitHub (Jul 29, 2021): Sorry, that was my bad. It was related to netbox_topology_view plugin activation. The problem has been solved.
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 status: revisions needed 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#5118
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?