Select culture/language when semantic model endpoint is added to the portal

Hi,

not sure about PBI Premium but if you are running on SSAS / AAS the sort order is defined by collation properties in Analysis Services. There isn't really a mapping between collation and culture as far as I am aware. While you would normally not, you can have different case-sensitivity and sorting settings than the normal.

I agree being able to specify this is useful, but you probably want to be able to set both Collation and Language / Culture. Additionally, being able to set global currency defaults would be useful.

As an example I am running:

Server:

• Collation: Latin1_General, Accent-Sensitive, Case-insensitive (& Kana- & width-insensitive)
• Language: English (United States)

Tabular database

• Collation: not explicitly set, so inherited from server
• Culture: en-US

Microsoft usually advises Finnish_Swedish_100 for Scandinavian countries. If you use 1033 / en-US you can benefit from faster hashing.

See: https://learn.microsoft.com/en-us/analysis-services/languages-and-collations-analysis-services?view=asallproducts-allversions and https://learn.microsoft.com/en-us/analysis-services/globalization-tips-and-best-practices-analysis-services?view=asallproducts-allversions

Hi Rory,

Culture alone works fine to use in this case.

I opened a model, deployed to an SSAS on prem instance from Timextender, in Tabular Editor. Collation was empty and culture was set to us-EN. In a Power BI report Å, Ä and Ö was sorted as A and O.

I changed culture to sv-SE in Tabular Editor and saved the bim-file. I left collation blank.Then I deleted the original database and deployed the altered on from tabular editor and processed. After that the sorting was correct.

On the database instances we always choose the Finnish-Swedish collation. But it don´t seem to have any impact in this case.

By the way, I don’t know if you have noted, but you can’t set collation for MDW’s in Timextender any more.

BR

Anders

Hi,

you are lucky I guess :-) I have had to deal with non-standard sortings for Frysian data in the past…

I had not noticed that you cannot set collation for DWH instances, good to know.