Solved

JSON Connection decimal seperator mixed up

  • 15 February 2023
  • 9 replies
  • 119 views

Badge

Hi, 

We are trying to connect to a REST api and are using the JSON CData provider version 22.0.8257.0.
We are connecting to two seperate datasources:

  1. Companies within Europe;
  2. Companies outside of Europe

The problem with the second datasource is that the decimal seperator is mixed up.
We tried some of the culture settings but it doesn’t seem to work.
What is the best way to solve this?

icon

Best answer by Michel van Drunen 27 February 2023, 15:24

View original

9 replies

Userlevel 6
Badge +5

Hi @Michel van Drunen 

Just to confirm this is the setting you have tried to adjust

https://cdn.cdata.com/help/DJH/ado/RSBJSON_p_Culture.htm

Which specific values have you tried for the culture setting? 

Can you please give an example of the values being returned, vs the desired output? 

Badge

Hi Christian,

I have added an image.
On the left side the desired output, in the middle the output (JSON) postman, on the right side the parquet file which is the input for TimeXtender. 
We tried culture setting nl-NL and we also tried to put the format in RSD file to string.
When no of decimals is 1 we have to divide the output by 10
When no of decimals is 2 we have to divide the output by 100
When no decimals the output is correct.
But we can’t determine the no. of decimals.

Userlevel 6
Badge +5

If you view the table in the data source explorer what data type is shown?

Which version of TimeXtender are you using?

Badge

Datatype float but tried several types by changing the RSD file, Version 6143.1

Userlevel 6
Badge +5

can you please try bringing it in as string/text and then converting later in a query table or in the DW table?

Userlevel 6
Badge +5

Hi Michel
 

Did you set the client culture as well?
 

You would set the client culture and then add either the same or something else in the culture field.

Userlevel 6
Badge +5

Hi @Michel van Drunen were you able to resolve the issue?

Badge

Hi Christian,

A colleague of mine will follow up this issue.
We have tried the culture settings but it seems to be wrong at the datasource level.
We have asked the supplier to change the api settings hopefully this will resolve the issue.

Kind regards,

Michel

Userlevel 6
Badge +5

Hi @Michel van Drunen did changing the api settings resolve the issue? please let us know if we can help further

Reply