Best Practices for Handling Different Regional/Cultural Settings

The best practice to avoid issues related to different regional/cultural settings is to use the same collation and settings for all the instances used if you intended to develop content to be rolled out globally.

Consider a scenario where you have a centralized engineering team located in one region/country and the production sites globally. When you configure the Development or Test servers with specific regional and culture settings and roll out the solution to production site servers where the regional/culture setting is specific with that region, you may have some issues while working with AVEVA Work Tasks.