Time zone configuration parameter should set up on Server site instead Client site
The impact would be the timestamp format in the published file in Azure Data Lake Store.
If we set PI integrator region to AU, the timestamp would be like 31/12/2019.
If we set PI integrator region to US, the timestamp would be like 12/31/2019.
If there are multiple support people and they use different region settings on their browser, it would mess up the data format in Azure Data Lake Store and this will cause an issue with data transformation process in Azure that we have.
I was thinking the setting should have been on a server level if we want to avoid this situation.
If the setting was intended to be on client side, I think it makes more sense that this is within each view so that data in each view can have customized data time format