decimal values are not taking when I run from published job
Hi Every one,
I am facing one strange problem in Insight 1.0.0.2 version. Let me explain you in brief here about my issues. I have server in France and they done the setup of windows 2008 enterprise server with 32 bit in France Keyboard language and then I installed the Insight 1.0.0.2 version. Every thing went well. But we come to know one problem at decimal values. In France we will have decimal as (,) comma instead of (.) dot so we changed the settings in control panel --> region language settings to US keyboard language. Now the problem is : I have created the job in Datamanager and inputting the values with decimal for 3 fileds, which type is decimal ( 10,2). When I run the job from datamanager then the values are inserting into right table. So published the same job and scheduled in Insight report server but its getting the insert into another table with rejected comment " Fields values should be numeric". But the same job is running from the datamanager not from the published job. Even I tried with scheduler also. Same behavior as similar published job. Some thing need to change at OS level to accept the decimal part when we schedule the job. Does any one know about it? I did fallowing test cases too: 1) Even I tested the databases in some other server its accepting the decimal values. 2) Job is run in another 3 windows box too Its looks strange to me. Can any one know any thing about it. Appreciate your gr8 help . Thanks, Om. |
2 answers
Hi Om,
I haven't tried your scenarios as France is not in support list of Insight 1002. Have you checked the Languages settings of your application server? |
Hi Jiang,
Yes, I checked in system level about the language. But not sure where exactly need to check with Insight tool. But When I install Insight I will select only English as language. Can you guide me how I can check the language set in applications? Thanks, Om. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.