when use api to change the ipam prefix custom fields, the change can't be displayed on the web. #7422

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

Originally created by @zhufall on GitHub (Dec 26, 2022).

NetBox version

v3.3.9

Python version

3.10

Steps to Reproduce

when I use the API to set the value for one prefix in custom fields and has checked using API, it looks like working well.
but, when I go back to check the web, the custom fields of the prefix still display the original state, with nothing to change.
20221226211437
20221226211600

Expected Behavior

the web displays the change when the API finished

Observed Behavior

with nothing changed on the web.

Originally created by @zhufall on GitHub (Dec 26, 2022). ### NetBox version v3.3.9 ### Python version 3.10 ### Steps to Reproduce when I use the API to set the value for one prefix in custom fields and has checked using API, it looks like working well. but, when I go back to check the web, the custom fields of the prefix still display the original state, with nothing to change. <img width="1253" alt="20221226211437" src="https://user-images.githubusercontent.com/60817674/209553054-45300ae6-80c8-4708-926e-aa60e386536c.png"> <img width="1631" alt="20221226211600" src="https://user-images.githubusercontent.com/60817674/209553060-cb14cca7-aad2-45fd-99ab-7d2c35301339.png"> ### Expected Behavior the web displays the change when the API finished ### Observed Behavior with nothing changed on the web.
adam added the type: bugstatus: revisions needed labels 2025-12-29 20:23:14 +01:00
adam closed this issue 2025-12-29 20:23:14 +01:00
Author
Owner

@kkthxbye-code commented on GitHub (Dec 26, 2022):

Please provide proper replication steps and make sure you replicate it on the newest version (3.4.1).

@kkthxbye-code commented on GitHub (Dec 26, 2022): Please provide proper replication steps and make sure you replicate it on the newest version (3.4.1).
Author
Owner

@markkuleinio commented on GitHub (Dec 30, 2022):

In the screenshot there is no command even attempted to save the custom field change to NetBox API, so this is not a NetBox issue with that information.

@markkuleinio commented on GitHub (Dec 30, 2022): In the screenshot there is no command even attempted to save the custom field change to NetBox API, so this is not a NetBox issue with that information.
Author
Owner

@hagbarddenstore commented on GitHub (Dec 30, 2022):

@zhufall You're missing w.save() as the last thing.

@hagbarddenstore commented on GitHub (Dec 30, 2022): @zhufall You're missing `w.save()` as the last thing.
Author
Owner

@jeremystretch commented on GitHub (Jan 2, 2023):

Closing this out as there's insufficient detail to warrant a bug report and there has been no further response from OP.

@jeremystretch commented on GitHub (Jan 2, 2023): Closing this out as there's insufficient detail to warrant a bug report and there has been no further response from OP.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7422