This post explains the issue in detail. Dates from FME Cloud are returned in UTC and you have to customize a workspace and associated functions to convert the time to the required zone. The handling of datetimes should be improved so the posted solutions (which I feel are a bit convoluted, especially the first one) are not required.
Archived
Better Handling of DateTimes on FME Cloud
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+14- Enthusiast
Forgot to add that while it does make sense to perhaps use UTC for FME cloud since the instance can be in a different timezone, the resulting current datetime behavior is not consistent with FME Server.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.