Dynamic model widget shows unfiltered value #7871

Closed
opened 2025-12-29 20:29:12 +01:00 by adam · 5 comments
Owner

Originally created by @apishark on GitHub (Apr 6, 2023).

NetBox version

v3.4.4

Python version

3.10

Steps to Reproduce

Browse to http://localhost:8001/dcim/devices/add/
Select a Manufacturer
Select a Device type
Select another Manufacturer

Expected Behavior

Device type shows filtered value

Observed Behavior

Device type shows unfiltered value

image
image

Originally created by @apishark on GitHub (Apr 6, 2023). ### NetBox version v3.4.4 ### Python version 3.10 ### Steps to Reproduce Browse to http://localhost:8001/dcim/devices/add/ Select a Manufacturer Select a Device type Select another Manufacturer ### Expected Behavior Device type shows filtered value ### Observed Behavior Device type shows unfiltered value ![image](https://user-images.githubusercontent.com/98494314/230364931-9e8be3a1-e427-4996-9145-563fbdeb683c.png) ![image](https://user-images.githubusercontent.com/98494314/230364986-e8c0d246-61c7-4b17-8314-6850a080edb8.png)
adam added the type: bug label 2025-12-29 20:29:12 +01:00
adam closed this issue 2025-12-29 20:29:13 +01:00
Author
Owner

@jeremystretch commented on GitHub (Apr 7, 2023):

Could you please clean up your description above? It appears you've pasted the same content twice under "steps to reproduce" and "expected behavior."

@jeremystretch commented on GitHub (Apr 7, 2023): Could you please clean up your description above? It appears you've pasted the same content twice under "steps to reproduce" and "expected behavior."
Author
Owner

@apishark commented on GitHub (Apr 7, 2023):

One is UNfiltered and the other is filtered.
In plain English, an unfiltered value is shown in the Device Type, which is not the expected behavior.

@apishark commented on GitHub (Apr 7, 2023): One is UNfiltered and the other is filtered. In plain English, an unfiltered value is shown in the Device Type, which is not the expected behavior.
Author
Owner

@jeremystretch commented on GitHub (Apr 7, 2023):

Ok, please update your description above to reflect that, rather the duplicating the reproduction steps in their entirety.

@jeremystretch commented on GitHub (Apr 7, 2023): Ok, please update your description above to reflect that, rather the duplicating the reproduction steps in their entirety.
Author
Owner

@apishark commented on GitHub (Apr 7, 2023):

NetBox version
v3.4.4

Python version
3.10

Steps to Reproduce
Browse to http://localhost:8001/dcim/devices/add/
Select a Manufacturer
Select a Device type
Select another Manufacturer
Device type shows unfiltered value

Expected Behavior
Device type shows filtered value

Observed Behavior
image
image

@apishark commented on GitHub (Apr 7, 2023): NetBox version v3.4.4 Python version 3.10 Steps to Reproduce Browse to http://localhost:8001/dcim/devices/add/ Select a Manufacturer Select a Device type Select another Manufacturer Device type shows unfiltered value Expected Behavior Device type shows filtered value Observed Behavior ![image](https://user-images.githubusercontent.com/98494314/230630840-a9626cd4-56f0-4b72-a5b1-46845517ad4d.png) ![image](https://user-images.githubusercontent.com/98494314/230630858-2956ba45-037d-494d-b9a9-d132841f0554.png)
Author
Owner

@kkthxbye-code commented on GitHub (May 10, 2023):

The manufacturer field does not exist in the device creation for in 3.5. The devicetype now has the advanced object selection field. As such there is nothing to fix here.

Also I'm not sure what the initial issue was. When we filter a DynamicModelChoiceField based on another DynamicModelChoice field we do not clear the currently selected value, but the filter is still applied to other non-selected values. I'm not sure if we wanted to change that, as it's pretty consistent throughout the UI.

@kkthxbye-code commented on GitHub (May 10, 2023): The manufacturer field does not exist in the device creation for in 3.5. The devicetype now has the advanced object selection field. As such there is nothing to fix here. Also I'm not sure what the initial issue was. When we filter a DynamicModelChoiceField based on another DynamicModelChoice field we do not clear the currently selected value, but the filter is still applied to other non-selected values. I'm not sure if we wanted to change that, as it's pretty consistent throughout the UI.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7871