Forum Discussion

sturlaws's avatar
sturlaws
Icon for Resident Rockstar rankResident Rockstar
7 years ago
Solved

Issue when opening a file in US setting

Hi,

 

I have made a power bi report for a customer. The customer has a US setting, while I have a european setting. When I send the file to the customer the semicolon separators are automatically converted to commas.

 

The report works fine, but when the customer tries to edit the DAX code, variuos error messages appears. Even if we make some very simple new measures in this fail, we get error messages. If we open a new file, writing the same simple test measures works fine. The DAX-formulas works fine when I open the file.

 

I have tried the following:

-send the report to the customer by email

-have the customer download the file from powerbi.com

-get the customer to download the latest power bi desktop version

-https://www.sqlbi.com/articles/changing-the-culture-of-a-power-bi-desktop-file/

 

Someone who has any tips on what to try next?

 

 

Need Help
  • sturlaws's avatar
    sturlaws
    7 years ago

    Checked the customers regional configuration, nothing looks out of order.

    Also messed around with my own regional settings to see if I could reproduce the issue, without success. 

     

    According to customer, changes to the dax code persists after pressing enter, despite the warning. Also the intellisense does not work because of the warning. Not a perfect solution, but it will have to do until I have time to rebuild the report, starting from scratch.

2 Replies

  • rafaelmpsantos's avatar
    rafaelmpsantos
    Icon for Responsive Resident rankResponsive Resident
    7 years ago

    It is probably a Regional Configuration of the customer computer.

    Go to Control Panel, Region, Additional Settings, and make sure that is all correct. You can click on reset to change to default settings.


    • sturlaws's avatar
      sturlaws
      Icon for Resident Rockstar rankResident Rockstar
      7 years ago

      Checked the customers regional configuration, nothing looks out of order.

      Also messed around with my own regional settings to see if I could reproduce the issue, without success. 

       

      According to customer, changes to the dax code persists after pressing enter, despite the warning. Also the intellisense does not work because of the warning. Not a perfect solution, but it will have to do until I have time to rebuild the report, starting from scratch.