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

custom-links - more information needed about available object fields #5936

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

Originally created by @ITJamie on GitHub (Jan 12, 2022).

Originally assigned to: @jeremystretch on GitHub.

Change Type

Addition

Area

Administration/development

Proposed Changes

re: https://demo.netbox.dev/static/docs/customization/custom-links/

from slack thread: https://netdev-community.slack.com/archives/C01P0FRSXRV/p1641996289144200

I couldnt find a documentation page that showed what values are available for the obj pointer.
I found out thanks to the slack thread that what i needed to access custom fields on the object was obj.cf.field_name

It might be good to have more details on the object values available?
depending on the datatype, these will be different i guess, vms vs devices vs racks etc

Originally created by @ITJamie on GitHub (Jan 12, 2022). Originally assigned to: @jeremystretch on GitHub. ### Change Type Addition ### Area Administration/development ### Proposed Changes re: https://demo.netbox.dev/static/docs/customization/custom-links/ from slack thread: https://netdev-community.slack.com/archives/C01P0FRSXRV/p1641996289144200 I couldnt find a documentation page that showed what values are available for the `obj` pointer. I found out thanks to the slack thread that what i needed to access custom fields on the object was `obj.cf.field_name` It might be good to have more details on the object values available? depending on the datatype, these will be different i guess, vms vs devices vs racks etc
adam added the status: acceptedtype: documentation labels 2025-12-29 19:34:30 +01:00
adam closed this issue 2025-12-29 19:34:30 +01:00
adam commented 2025-12-29 19:34:30 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 14, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 14, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
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: accepted type: documentation
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#5936
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?