question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Incorrect handling of null value in custom fields

See original GitHub issue

NetBox version

v2.10.6

Python version

3.6

Steps to Reproduce

  1. Have existing custom field with empty value (in my case it’s dcim > device custom field)
  2. Update from NetBox 2.9.11 to 2.10.6
  3. Add new device and leave this custom field empty while creating it
  4. Value of this custom field will be “” (empty string) instead of null

Expected Behavior

Value of empty custom fields should be null

Observed Behavior

Value of empty custom fields is “” (empty string). Devices that have been added prior to update to NetBox 2.10.6, still have proper value null for empty custom fields.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5

github_iconTop GitHub Comments

1reaction
karlismcommented, Aug 24, 2021

@jeremystretch, thanks! Just upgraded NetBox to 2.11.12 and verified that it is working properly now.

Any suggestions on how to fix all previously created devices that have "" instead of null value?

0reactions
karlismcommented, Jul 8, 2021

I guess that this issue is also related: https://github.com/netbox-community/netbox/issues/6686

Read more comments on GitHub >

github_iconTop Results From Across the Web

Searching by a custom field with invalid value/option results in ...
Scenario 1. There is a null value in the customfieldoption table. When a search is performed, it will search for all the custom...
Read more >
ColumnSet Problem with CRM Null Value Custom Fields
I have one particular custom field I created on CRM that I could not retrieve by ColumnSet. I read that a column could...
Read more >
Getting errors with null fields - Power Automate | Microsoft Learn
If a flow runs with a null field, it will cause: Wrong behavior: flow action's input is receiving null field, when it expects...
Read more >
Cannot Be Null for Custom Field! Error - IFS Community
If the field is coming through as null by default that should be what you want. Stop the insert (or edit) unless the...
Read more >
Custom field contains Invalid value {null} for EMAIL data type
Need help troubleshooting a rule error message: Custom field contains Invalid value {null} for EMAIL data type.I have a number of email ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found