TM1 Forum

I have searched through the docs and have not found anything to help. We have begun implementing our Canadian locations and they are using the localization settings French (Canadian). The issue is we are seeing different behavior between Excel and Web.

The templates are using the NOW function and pulling some info from TM1. When I look in Excel my dates are correct, but when I look in TM1Web it is not finding the information correctly. Even more strange is that some of the French PC's work and some do not work. Can anyone help me out as to where to look? I have never worked with localization before so I am kind of at a disadvantage.

As far as an environment

Version 9.1 SP2 U3

64 bit Server in English (United States) localization

The clients are all XP

George Regateiro wrote:I have searched through the docs and have not found anything to help. We have begun implementing our Canadian locations and they are using the localization settings French (Canadian). The issue is we are seeing different behavior between Excel and Web.

The templates are using the NOW function and pulling some info from TM1. When I look in Excel my dates are correct, but when I look in TM1Web it is not finding the information correctly. Even more strange is that some of the French PC's work and some do not work.

Can you be more specific when you say that it's "not finding the information correctly"? What exactly is it displaying? What's the format that you're using for the cell(s) in question?

(I just tested a websheet by creating the now() function in two cells of a websheet (one using the default format, one using a custom format including the name of the day of week), then set my own PC's regional setting to French Canadian. Aside from seeing the whole of TM1 Web presented to me in French (a rather scary experience for a non-Francophone), the dates rendered correctly for the region including the short date format having a leading year.)

office mui install on the webserver can solve some issues
but what exactly doesn't work ?

Sorry I started to explain the problem and then I kind of stopped.

Our templates use the Now () function in Excel to get the current date, this result will then be used in a DBRW to a control cube that is set up with some period definitions. The templates then use the value returned by this control cube to populate the user's display.

When I open up the template in excel on the French machine this sequence works, but from the same computer this sequence is not working through the web, the periods are not properly loading since either Now is not returning a value or the DBRW does not know how to handle the value that is being passed in from the Now function. Since it works on the client I cannot tell which one is actually breaking through web.

I know it is the localization since I have been able to test it on one of my machines. With the localization to English the web template works fine, once I switch the computer to be French (Canadian) the web template no longer works.

I will try the suggestion about the MUI on the server. I saw that in the docs for the clients, but I did not see that mentioned for the server, but the more I have read about the localization the more it makes sense. When I first encountered the problem I was mistaken as to how the localization was processed on the web server side.

Having only dealt with single region setups I am not an expert on windows localisation settings. The fact that it is working on a client's machine with French settings but not on the web points to the version of Excel running on your web server. Or more specifically the localisation settings available to / installed for the logon that the TM1ExcelService is running under.

I thought I would put this out there as an update since I discoveded the issue.

The actual problem was in the format string that was being used in template. Since French Canadian numbers use the "," in place of the decimal the format string was processing incorrectly. So the now function was bringing back the entire decimal rather then just the whole number. We have since switched to using today to bring back only the whole number part of the date serial number.