# Issues with date type converter format string **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [October 21, 2021, 9:49am UTC](https://community.graylog.org/t/issues-with-date-type-converter-format-string/21524 "2021-10-21T09:49:57Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![Winklerschulbedarf](https://avatars.discourse-cdn.com/v4/letter/w/ec9cab/32.png) [@Winklerschulbedarf](https://community.graylog.org/u/Winklerschulbedarf)\ **Post date:** [October 28, 2021, 8:46am UTC](https://community.graylog.org/t/issues-with-date-type-converter-format-string/21524/12 "2021-10-28T08:46:35Z")
Hello guys! Sorry i was very busy the last days and had no time to test out stuff. But i finally got it working again using a mix of extractor and pipeline. Heres how i did it: 1. Create an extractor to copy the timestamp from the message into a second timestamp field. ![grafik](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/5/5b1ca1c10e01256ac42831a70465b3ae27a6e74c.png) 1. Create a pipeline on the stream that gets the messages you want the timestamps to get changed. ![grafik](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/f/f4f52f650b32ae223ae579b581a7e2a949f2c638.png) Edit: You can also use **has\_field(“msg\_timestamp”)** instead of **true** if you want to. 1. Change the message processor order under System \> Configurations to the following: ![grafik](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/c/c509c5f7a8b4fbe6a1b2dfaedf3b274185c9828a.png) Its important that the Message Filter Chain comes before the Pipeline Processor! Of course you could do everything with the pipeline instead of using a mix but at this point i was just to lazy. I hope i didnt forget anything. If so just ask me and i will try to help you out. Thanks for the help guys! --- _[View the full topic](https://community.graylog.org/t/issues-with-date-type-converter-format-string/21524)._