Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi there,
today I stumbled upon something interesting that cannot be a desired behaviour.
If the application language of Power BI Desktop is English, then the default name for the first query in the new DAX Query View is 'Query 1'. So far so good. But in my case - I am working with the German version of PBI Desktop. In this case the default name of the initial query view is 'Abfrage "1"'. Note the quotation marks.
This is actually quite some problem, because it leads to the unexpected behaviour that I am unable to save the entire pbix file the moment I start to use the new DAX Query View and execute a query with this default name. First I was confused, why I could not save my file anymore. Every time I tried to save it, I got an error thrown which states ""C:\...\..." ist kein gültiger Dateipfad." which means the target path is not a valid file path.
So I looked up the error details and found the topmost entry of the stack trace, which was the following:
"bei Microsoft.PowerBI.Client.Windows.Services.PowerBIFileSerializer.ValidateDaxQueryFileName(String fileName)"
The corresponding stack trace message was: "The file name 'Abfrage "1".dax' contains invalid characters."
It appears that the default query name - which is not user generated but comes from the product itself - is an invalid query name. The quotation marks are crucial. I removed those in my Query view and suddenly I was able to save my file again.
I hope you guys get rid of those quotation marks as soon as possible, because this is a serious issue. The user suddenly becomes unable of saving the entire pbix file just by using the new DAX Query View. And the critical part is, that at first sight you have no clue what is causing this problem. Only after a deep dive in the error logs advanced users may identify the problem.
Maybe there are even more languages affected, I have not tested it for others than English and German.
Best regards and happy holidays
Tim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.