Developer forum

Forum » Integration » Error getting culture: Culture is not supported

Error getting culture: Culture is not supported

Lars Larsen
Reply

Hi,

I am trying to export some orders with the Data Integration. The problem is that I want prices to use a dot as the decimal separator. I have therefore selected "US" in the "Number format culture" field in the destination settings of my export job. But when I run the job I get this error: "Error getting culture: Culture is not supported". The orders are exported to the xml file, but prices are with dot as decimal separator and not comma as I want.


Replies

 
Nicolai Høeg Pedersen
Reply

Culture should be en-US or da-DK, see here: https://msdn.microsoft.com/en-us/library/bb975829.aspx

 
Lars Larsen
Reply

Hi Nicolai

Oh, sorry I made a typo in my last post. I wrote: "The orders are exported to the xml file, but prices are with dot as decimal separator and not comma as I want.". But it should have been opposit: "The orders are exported to the xml file, but prices are with comma as decimal separator and not dot as I want."

So I want the decimal separator to be a dot. Therefore I chose "US" in the dropdown "Number format culture". As the manual states"Choosing a language from dropdown will pass the culture information explicitly (ie "da-DK" or "en-US")". But I don't think "en-US" is passed because the decimal separator is still a comma in the outputted XML file.

 
Dmitriy Benyuk
Reply
This post has been marked as an answer

Hi Lars,

To check if the "US" selection stores the correct number culture (which must be "en-US" in this case) please go to the ManagementCenter->Ecom->Internationalization->Countries and

open the "USA" country and check if the field "Locale ID" has a value of "en-US" like it is show in the attached picture.
If it doesn't have this vale you need to update it and save the country, after that you need to re-save your Data Integration job with update of the Xml Provider destination settings:
open your job and click on "Edit destination settings", and select the US country from the drop-down and then click "Save changes" button.

One note regarding the fields: only the fields whoose source type is float, decimal, double are taking into account when the culture formatting is applied.

Best regards,
Dmitrij

en-US_locale.png
Votes for this answer: 1
 
Lars Larsen
Reply

Hi Dmitriy

That did the trick. In the country settings for "USA" the field "Locale ID" was set to "US". I changed it to "en-US", and updated my data integration job and it worked. Great, thanks a lot smiley

 

You must be logged in to post in the forum