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

Sorting Jobs table by object causes FieldError #8823

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

Originally created by @cpmills1975 on GitHub (Nov 8, 2023).

Originally assigned to: @cpmills1975 on GitHub.

NetBox version

v3.6.4

Python version

3.8

Steps to Reproduce

  1. Browse to /core/jobs
  2. Click on the 'object' heading in the table, observe nothing happens (HTMX request results in 500 server error, but this is not visible - see below)
  3. Try and reload the page, observe that an exception is thrown and all further attempts to view the Job listing page results in the same exception:

<class 'django.core.exceptions.FieldError'>

Field 'object' does not generate an automatic reverse relation and therefore cannot be used for reverse querying. If it is a GenericForeignKey, consider adding a GenericRelation.

Python version: 3.8.10
NetBox version: 3.6.4
Plugins:
netbox_demo: 0.3.1

When attempting to sort by object, Django will throw a FieldError meaning the HTMX request appears to do nothing. The error can be observed in the browser console. Subsequently, the FieldError becomes visible when reloading the page, because sorting by object is now stored in the user's preferences.

In case anyone stumbles across this, the fix is to remove the table configuration for the JobTable from the user preferences or remove the ordering by appending ?sort= to the /core/jobs URL.

Expected Behavior

The Jobs list should either return a list sorted by the object, or shouldn't allow the table to be sorted by the object field at all.

Observed Behavior

A FieldError exception is raised.

Originally created by @cpmills1975 on GitHub (Nov 8, 2023). Originally assigned to: @cpmills1975 on GitHub. ### NetBox version v3.6.4 ### Python version 3.8 ### Steps to Reproduce 1. Browse to /core/jobs 2. Click on the 'object' heading in the table, observe nothing happens (HTMX request results in 500 server error, but this is not visible - see below) 3. Try and reload the page, observe that an exception is thrown and all further attempts to view the Job listing page results in the same exception: > <class 'django.core.exceptions.FieldError'> > >Field 'object' does not generate an automatic reverse relation and therefore cannot be used for reverse querying. If it is a GenericForeignKey, consider adding a GenericRelation. > >Python version: 3.8.10 >NetBox version: 3.6.4 >Plugins: > netbox_demo: 0.3.1 When attempting to sort by object, Django will throw a FieldError meaning the HTMX request appears to do nothing. The error can be observed in the browser console. Subsequently, the FieldError becomes visible when reloading the page, because sorting by object is now stored in the user's preferences. In case anyone stumbles across this, the fix is to remove the table configuration for the JobTable from the user preferences or remove the ordering by appending ?sort= to the /core/jobs URL. ### Expected Behavior The Jobs list should either return a list sorted by the object, or shouldn't allow the table to be sorted by the object field at all. ### Observed Behavior A FieldError exception is raised.
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 20:41:43 +01:00
adam closed this issue 2025-12-29 20:41:43 +01:00
adam commented 2025-12-29 20:41:44 +01:00
Author
Owner
Copy Link

@cpmills1975 commented on GitHub (Nov 9, 2023):

I've raised PR #14226 for this if you are happy to accept?

@cpmills1975 commented on GitHub (Nov 9, 2023): I've raised PR #14226 for this if you are happy to accept?
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 severity: low 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#8823
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?