custom field value not shown in summary #10851

Closed
opened 2025-12-29 21:36:41 +01:00 by adam · 2 comments
Owner

Originally created by @lucafabbri365 on GitHub (Mar 5, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.2.4

Python Version

3.10

Steps to Reproduce

  1. Create a custom field:
    • Name: last_ping_check
    • Type: Date & time
    • Object type: IPAM > IP Address
  2. Update custom field for an IP Address via API (Date & time format is: yyyy-MM-ddTHH:mm:ssZ (UTC))

Image

Expected Behavior

I expect to see the value of Last Ping Check in IP address summary view.

Observed Behavior

The Last Ping Check is empty in IP address summary:

Image

...despite the information is present (Edit mode):

Image

If I simply cut and paste the value into the same field and save, it becomes visible:

Image

Originally created by @lucafabbri365 on GitHub (Mar 5, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.2.4 ### Python Version 3.10 ### Steps to Reproduce 1. Create a custom field: - Name: **last_ping_check** - Type: **Date & time** - Object type: **IPAM > IP Address** 2. Update custom field for an IP Address via API (Date & time format is: `yyyy-MM-ddTHH:mm:ssZ` (UTC)) ![Image](https://github.com/user-attachments/assets/dbc53641-6a7f-4dc4-aa1a-c3de7ea7d1f8) ### Expected Behavior I expect to see the value of **Last Ping Check** in IP address summary view. ### Observed Behavior The Last Ping Check is empty in IP address summary: ![Image](https://github.com/user-attachments/assets/b189f83f-b406-4f22-b92b-fa5bcd14d370) ...despite the information is present (Edit mode): ![Image](https://github.com/user-attachments/assets/7b3b835b-fbd0-45c3-8118-26ecca56d850) If I simply cut and paste the value into the same field and save, it becomes visible: ![Image](https://github.com/user-attachments/assets/49b842de-3e00-47f3-8a62-248b74286656)
adam added the type: bug label 2025-12-29 21:36:41 +01:00
adam closed this issue 2025-12-29 21:36:41 +01:00
Author
Owner

@lucafabbri365 commented on GitHub (Mar 5, 2025):

Hello,
my fault. I used a wrong Date & time format: instead of YYYY-MM-DD HH:MM:SS I used yyyy-MM-ddTHH:mm:ssZ.

@lucafabbri365 commented on GitHub (Mar 5, 2025): Hello, my fault. I used a wrong **Date & time** format: instead of `YYYY-MM-DD HH:MM:SS` I used `yyyy-MM-ddTHH:mm:ssZ`.
Author
Owner

@jeremystretch commented on GitHub (Mar 5, 2025):

I remember addressing a bug related to this a while back, and it came down to a semantic difference between ISO 8601 and RFC 3339. IIRC the format with the T separating the date and timestamp is compliant per both standards so that's what NetBox uses for serialized data.

@jeremystretch commented on GitHub (Mar 5, 2025): I remember addressing a bug related to this a while back, and it came down to a semantic difference between [ISO 8601 and RFC 3339](https://stackoverflow.com/questions/522251/whats-the-difference-between-iso-8601-and-rfc-3339-date-formats). IIRC the format with the `T` separating the date and timestamp is compliant per both standards so that's what NetBox uses for serialized data.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10851