When working on a Excel document in Sharepoint when I use the TODAY function I get odd results. It looks like the date is from the day before. I wonder what timezone does it use? Is that a setting or is it based on the browser I use?
(Context: I'm using Sharepoint on a Kubuntu 20.04 desktop)
That based on the timezone you specify in site settings->Regional settings. As the below picture shows:
We are facing an issue at our project related to date parameters where after changing the date with the date picker it changes the date format.
We use the Canadian format dd/MM/yyyy but report date picker showing (yyyy-dd-mm).
we use CRM 2011 in SSRS 2012.
There are no custom logic on the parameter at all.
After clicking the report view button in the report then date picker value has changed to below?
We have tried below option and still we are experiencing the same issue for all the reports which use date pickers:
Modifying regional settings on CRM server
Modifying regional settings on SSRS server
Modified user regional settings in control panel
Modified browser language settings
Changing global date format in CRM organization
Changing the personal date format in CRM options
Adding a Language element to the report .rdl
Modifying the date format by javascript
Modifying the report viewer control on the CRM and SSRS servers
Separating Date and Time portions of the date parameter
we have installed RU 18 and still issue was not fixed.
After that we have done Long days of investigation and we were able to fix this issue by below way.
we have opened report viewer page in below folder in CRM server and update culture of the page to Culture="en-US"
C:\Program Files\Microsoft CRM\CRMWeb\CRMReports\rsviewer
QuirksReportViewer.aspx page
<%# Page language="c#" Inherits="Microsoft.Crm.Web.Reporting.RemoteSrsReportViewer" AutoEventWireup="true" EnableViewState="true" EnableEventValidation="false" Culture="en-US"
I'm having a lot of trouble deploying a website on windows azure... with dates and money formats, for example. My question is: It is possible to change the server's culture, or do I have to change my entire app to fits the azure location settings?
Works fine on servers with Latin American standards.
You can add something like this to your web.config (in the system.web section):
<globalization uiCulture="en" culture="en-GB" />
You can find the appropriate identifier in the CultureInfo Class.
I believe you'll need to change the culture settings in your application. Here's a similar thread - Currency settings in Azure
I want to add some OSIsoft RtWebParts to a Sharepoint page. I want these trends to be shown in different timezones for different users. What I'm finding is that they are always shown in EDT.
Ideally, I want a solution for configuring the presented timezone by page or by user.
Michael,
I am the product manager at OSIsoft for RtWebParts.
The time zone is controlled by the SharePoint site, not the web server. One possible workaround it to create a SP site for each time zone that you would like to support. Unfortunately, you would then face the challenge of maintaining the content for multiple sites.
I would also like to make a correction to the workaround that is described above. The workaround should use the RtActiveView web part(which uses ProcessBook .pdi files), not RtGraphic (which uses ProcessBook .svg files).
Thanks,
Tamara
The official response from OSIsoft is: this cannot be done.
RtWebparts objects always use the timezone of the Sharepoint site hosting them. Period.
Other than spinning up a new sharepoint site for each timezone you care about, there is one unappealing workaround:
Create your display in ProcessBook wherein you configure the time offset as desired
Include the ProcessBook PDI file within an RtActiveView web part
Repeat for each timezone
You're still stuck with one timezone (set in the SVG) but now at least you can get multiple timezones without multiple servers.
I've got a hosted VPS hosted by a UK hosting company that for some reason is set to US settings. In fact, until recently, the regional settings were 'English - United States'. I've corrected the regional settings, but my application is still working with the wrong date format. See:
http://www.albaassoc.com/events/listevents.aspx
The default dates are supposed to be the current date to the date + 3 months, but as you can see, the dd and MM fields are swapped. Note: the AJAX calendar extender is manually set to dd/MM/yyyy so that is why the calendar pop thinks we are interested in June/July rather than January!
I know there are various ways to set a page or an application to use a particular locale, but I'd rather go for a global approach.
Is it possible to re-configure IIS to work in a different locale, or if not, can I tweak machine.config so that it is a once-only change?
I've got a ticket open with the host but I'm not going to hold my breath - they aren't going to want to reinstall IIS...
Thanks in advance.
Via the globalization element, you can set the culture and uiculture for a site (via web.config) or the entire machine (via machine.config).
I just got a similar issue (Windows Server 2008, IIS 7). I was able to fix it by editing the web config file, but like you I wanted a global fix.
The solution is in the config panel, regional settings. I don't know for you (what's your OS), but under WS2008, there is an administrative tab under regional settings. It allows you to copy the settings of your logged in user (you) to the administrative accounts (network services in this case). Rebooted and got it right.
The problem is often that the user running either IIS or the application pool your app belongs to is a system account which was created when the server was installed. They therefore inherited whatever the default locale was at the time.
If you can't fix it in regional and language options you can always try editing in the registry directly (with the usual proviso that messing around with the registry can seriously muck up Windows). The regional settings are all under HKEY_USERS\{userid}\Control Panel\International - if you compare what's there for each user with what you have under HKEY_CURRENT_USER\Control Panel\International it should be fairly obvious what to change. I've done this a few times on Windows 2000 servers and it's worked OK.
The other option is just to create a new user on the machine with the correct locale and then set both IIS and the application pool to run with that identity.
Bit of an old thread, but I still look after some legacy Classic ASP sites written by the now defunct Aztec civilisation in praise of their feathered gods.
A server move prevented all the date code from working and sacrificing a chicken was no help, so here is the very easy solution in IIS 7 that has not been mentioned, possibly because no-one else is suffering like me.
Go to IIS Manager.
Select either the root server node to apply to all sites, or select the site node you are having problems with if you want to leave the server default alone.
In IIS section, double click ASP icon.
Set Locale ID to your desired locale (2057 for UK).
This should take effect immediately.
Alternatively you could go buy a DeLorean, go back in time and kill the programmer who decided FormateDateTime(d, vbLongDate) was the best way of generating a date to be used in the database. Or persuade the client to give me a lot of money to replace the whole thing. Either's good.
I had a problem, with having the the date formatted mm/dd/yyyy when I wanted it to be dd/mm/yyyy.
I am using windows server 2003 and IIS 6
The solution was to add the following to any web config file, then reboot your server and it should work just fine.
<globalization requestEncoding="utf-8" responseEncoding="utf-8" culture="en-GB" />