- Issue created by @keiron
- 🇩🇪Germany jurgenhaas Gottmadingen
Nice one, thanks @keiron for posting this together with your sample.
The issue is a simple one: you're storing the timestamp into your custom field, but it requires the date in the format
2023-03-01T00:00:00
. So, if you convert that with the patternY-m-d\TH:i:s
it'll work.This is outside of ECA's control, what the required data format is for the various field types. The best way to figure it out is to store a field value through the interface and look into the database to see in which format it's being stored. Then you can easily replicate that.
- 🇬🇧United Kingdom keiron
Fantastic, thanks for the speedy response Jurgen! I'm glad it wasn't a bug and I'll know to look in the database for the format in the future.
Keiron
- Status changed to Fixed
almost 2 years ago 1:14pm 2 February 2023 - 🇩🇪Germany jurgenhaas Gottmadingen
Great, have fun with further ECA-modelling ;-)
Automatically closed - issue fixed for 2 weeks with no activity.