Errors with dots and commas (decimal separator)

dataservices job design
1

Hi All,

We are suddenly facing issues with the values.

We actually use ‘comma’(,) as a decimal separator instead of dot (.). At the first stage, BO reads the values correctly, (20,000000) and in the next step it is multiplying with the number of values present after comma. Please find attached screenshot for more information. Can someone pls help me in tracing this, how all of sudden this issue is happening. WE have similar issue where ever we load numerics.

We have verified the server regional settings, it is set correctly where the decimal separator is comma.

Please let me know if you need more info on this.

Thanks a lot in Advance,

LK
Decimals being multiplied.doc (44.0 KB)

klkreddy83 :uk: (BOB member since 2011-03-07)

2

I think there is a setting for this. Someone played with DSConfig by any chance? I will check and see…

ganeshxp :us: (BOB member since 2008-07-17)

3

Can you Explain a little bit more on the type of source you use?
is it a Flat file?

Also when you say, you have a similar issue where ever you load Numeric values.

Is it happening for the same kind of source file (Flat File etc) ?

Tarunvig :us: (BOB member since 2011-01-18)

4

Hi Tarun,

The source files are excel and txt files. Previously, the output numerics are displaying as 123,00 but now its 123.00.

Yes, it is happening for most of the jobs we load thru excel and txt files.

Hi Ganesh, Can you please suggest me if you have got the answer.

FYI, below line appears in dsconfig.txt file for decimal separator.

“LAZY_DECIMAL_CONVERSION=TRUE”
“#Decimal_separator=,”

There is also an other issue we are facing, “Numeric value out of range”. I tried changing the BO job accordingly, but BO is throwing an error for the same files which had run successfully in the past runs.

Is anything changed in settings?
Thanks,

Lakshmikar

klkreddy83 :uk: (BOB member since 2011-03-07)

5

At least for flat files the decimal format is completely locale dependent. Meaning if you moved to a server with a different format this might be causing problems. For flat files you can specify the format explicitly in the file format editor. Sadly you will have to do that per column. As far as I remember, setting the locale in the file format editor does not help for the number format but I’m not quite sure about that.

For excel files there shouldn’t really be a format since the content is an actual number and how it is displayed should be excel’s problem. I don’t see how you need to convert anything there, you should never have the number as a string represneted in the first place.

HerdplattenToni (BOB member since 2011-05-13)

6

Yes that decimal separator is commented. Is your complete environment a system that would need , as a decimal separator or only this specific stuff?

ganeshxp :us: (BOB member since 2008-07-17)

7

Hi Toni, Thanks for your response. I have verified the windows server format, it is using the same Dutch format (being comma as decimal separator)

If i need to specify the format for all the columns in file format editor, then i would need to edit this for many jobs which is causing same problem.

Hi Ganesh,

our complete environment should have the same setup of comma as a decimal separator. I see in BODS data store configuration, the decimal separator is dot, I tried changing this but throwing an error. :hb:
Can you pls suggest me if there are some settings to be changed.

Thanks,

LK

klkreddy83 :uk: (BOB member since 2011-03-07)