Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow custom field objects to be limited #16169

Open
karolyczovek opened this issue May 16, 2024 · 6 comments
Open

Allow custom field objects to be limited #16169

karolyczovek opened this issue May 16, 2024 · 6 comments
Assignees
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: revisions needed This issue requires additional information to be actionable type: feature Introduction of new functionality to the application

Comments

@karolyczovek
Copy link

NetBox version

v3.7.8

Feature type

Data model extension

Proposed functionality

Is it possible, to set custom fields to honor relations?

For example, I set a custom field related to the site as multi-object with prefixes, then let the custom field honor the global/site-assigned specific prefixes.

Use case

Multi-field custom field object I could select from prefixes already assigned to site.

Database changes

No response

External dependencies

No response

@karolyczovek karolyczovek added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels May 16, 2024
@jeffgdotorg
Copy link
Collaborator

Thanks for your interest in helping improve NetBox.

I think your proposal makes sense, but since you've opened it against 3.7.8, I wonder whether the same effect might be possible with no code changes by leveraging improvements to the select controls in NetBox 4.0.

In the screenshot below, you can see that the description of a prefix now shows up in the custom field select control, and that by using type-ahead filtering you can limit the values shown. Assuming your prefixes have descriptions, I think this workflow might meet your need. Please give it a try in a test environment or on the [public demo system[(https://demo.netbox.dev/) and indicate whether you agree.

image

@jeffgdotorg jeffgdotorg added status: revisions needed This issue requires additional information to be actionable and removed status: needs triage This issue is awaiting triage by a maintainer labels May 17, 2024
@karolyczovek
Copy link
Author

Will give it a try, does 4.0 API already work with Ansible?

@karolyczovek
Copy link
Author

Just run the smoke tests - UI-wise it looks fine but still an extra effort from the enduser - however ansible interaction (lookups and modules) are broken from 4.0

@jeffgdotorg
Copy link
Collaborator

Top people are working on the remaining 4.0 compatibility issues in the Ansible collection. I understand that may be a barrier to you upgrading your instances, but let's please keep the comments in this issue on topic to avoid confusing future time travelers.

@karolyczovek
Copy link
Author

Same applies in general - imagine sites with same-like named equipments - for example 16 sites with 20 cameras at each named camera NN, so custom field "related objects" would be nice to honor site

Copy link
Contributor

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: revisions needed This issue requires additional information to be actionable type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants