Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
Hello,
We're using cB in 2.1.0.3 version, and we encountered a problem related to date fields - when exporting data from a created report to Excel, only default date fields adjust their value to the user's time zone. Custom fields retain their value regardless of the time zone of the user who generates the report. This causes problems with creating KPI reports, for example:
The KPI is calculated based on a comparison of two fields: the default Closed at field and the custom due date field. When Closed at exceeds the due date, the task is marked as delayed.
The user (time zone +01:00) set the value of the custom due date field to 13.10.2024 15:00. The task was closed on 13.10.2024 13:00.
When a user in the +07:00 time zone generates a report with these hours, from his perspective the task is delayed because the due date field value remains the same (13.10.2024 15:00), and Closed at has adjusted to his time zone (13.10.2024 19:00).
Is there any way to systemically equalize these values while maintaining the ability to configure zones for employees?
Hi @PW_10729315
Thank you for your question!
Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.
Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.
Best regards,
Hello,
please be informed that this is a known issue that has already been reported to the Development team.
Currently, there is no scheduled release date for the fix.
Related Article:
Best Regards,
Istvan