Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Solved! Go to Solution.
I found the issue - the culprit was an underscore instead of a hyphen in a locale in the PowerQuery for the partition definition that somebody inserted manually in the .bim file (source of the Tabular Model).
#"Changed Type" = Table.TransformColumnTypes(#"Promoted Headers",{{"datum_key", type date}, {"tijd_key", Int64.Type}, {"apparaat_key", type text}, {"garage_key", type text}, {"bronsysteem_key", type text}, {"betaalwijze_key", type text}, {"product_key", type text}, {"betaling_atl", Int64.Type}, {"betaalregel_omzet_bdg", Currency.Type}, {"betaalregel_btw_bdg", Currency.Type}}, "en_US")
Locally this was not causing issues but in the PowerBI service this caused the following symptoms:
Fixing the locale fixed the issues for me. While I'm happy that I found the issue, I'm not amused by the lack of developer support in PowerBI and Visual Studio...
I would expect these things at least:
Hi @Anonymous
What I would suggest doing is to install Tabular Editor and view the meta data that way and see if there are any pointers there to see why it is not working?
I typically in the past have used Power BI Desktop and then used ALM Toolset and Tabular Editor to deploy and make changes. I know it is not visual studio but I would be hesitant to use visual studio because it does not have all the Power BI related updates.
I found the issue - the culprit was an underscore instead of a hyphen in a locale in the PowerQuery for the partition definition that somebody inserted manually in the .bim file (source of the Tabular Model).
#"Changed Type" = Table.TransformColumnTypes(#"Promoted Headers",{{"datum_key", type date}, {"tijd_key", Int64.Type}, {"apparaat_key", type text}, {"garage_key", type text}, {"bronsysteem_key", type text}, {"betaalwijze_key", type text}, {"product_key", type text}, {"betaling_atl", Int64.Type}, {"betaalregel_omzet_bdg", Currency.Type}, {"betaalregel_btw_bdg", Currency.Type}}, "en_US")
Locally this was not causing issues but in the PowerBI service this caused the following symptoms:
Fixing the locale fixed the issues for me. While I'm happy that I found the issue, I'm not amused by the lack of developer support in PowerBI and Visual Studio...
I would expect these things at least:
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.