Support date type in customFields
L
Lovelace
Using the Users API it's currently not possible to set a custom-field such as LastSeenTime to a string value that is a valid DateTime e.g.
2024-04-01T12:38:47Z
or even just 2024-04-01 12:38:47
is rejected and an empty string is stored for the use instead.Any invalid date stores correctly e.g.
2024-03-99T12:38:47Z
As do just dates or times.
However, there's a work around which is to add a prefix or suffix to store a DateTime.
Sarah Hum
Thank you for posting, Lovelace! I have a few more questions for you:
- Can you provide more details on how you intend to use the date type in customFields?
- What is the impact of this issue on your usage of our API?
- Can you share more about the workaround you mentioned? How does it affect your workflow?
L
Lovelace
We've decided to store dates, over date times, as that gets us what we need here.