You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many files inside pbit zipped directory (i.e. Connections, DataModelSchema, DiagramLayout, DiagramState, Metadata, Settings, Version, Report/Layout, Report/LinguisticSchema) are json files enconded with UTF-16 LE. This makes it difficult for versioning repos to diff them.
The Power BI desktop software needs those file to be encoded like this to work.
This way, it's a nice feature to convert those files to UTF-8 on pre-commit, and convert them back to UTF-16 LE on post-commit and post-checkout.
The text was updated successfully, but these errors were encountered:
I could do it with iconv, but I had some problems because I formatted the json files with jq, and when I formatted back, Power BI didn't recognize the pbit file.
Probably using iconv to convert back and forth will solve it, and working with jq will be another step on another enhancement
Many files inside pbit zipped directory (i.e.
Connections
,DataModelSchema
,DiagramLayout
,DiagramState
,Metadata
,Settings
,Version
,Report/Layout
,Report/LinguisticSchema
) are json files enconded withUTF-16 LE
. This makes it difficult for versioning repos to diff them.The Power BI desktop software needs those file to be encoded like this to work.
This way, it's a nice feature to convert those files to
UTF-8
onpre-commit
, and convert them back toUTF-16 LE
onpost-commit
andpost-checkout
.The text was updated successfully, but these errors were encountered: