Forum Discussion
PBIP Git Integration Errors
I did some more experimenting, and I came to the following conclusions:
Sync from git to workspace does not work with an empty PBIP (meaning no tables and measures in the data model and no report objects). After adding a manual entry table to the PBIP and the git sync worked. I suppose this is fine, but a better error message should be added.
I added a table from a snowflake data warehouse connection and added some measures (and used them in report objects), and it continued to sync successfully. No issue there.
I added a simple measure group with tabular editor and used them in some report objects. The sync was still successful. So measure groups appear to be supported.
I added a table based on query from a snowflake data warehouse and manually manipulated the extended properties to make it a field parameter table (which is a common use case for me). This caused the sync to fail. So either field parameters are not supported or my odd use case isn't.
Field parameters are supported.
Did you add the extended properties by yourself using Tabular Editor or using Power BI Desktop? Can you share a bim file?
Yes, I added the external properties myself with tabular editor. My use case involves using the same PBIX for many environments so I have the need to dynamically populate my field paramters. I achieve this by importing a SQL table that mimics the structure of a field parameter table with the extended properties added to the imported table. BIM file attached.
Not sure if I can attach files here so here is a link to a public repo with the model.bim: dlomartra1/powerbi-git-example (github.com)
I'm assuming you can deploy your BIM file using XMLA and work with the field parameters in the service, correct?
Have you compared your bim file and extended properties to the extended properties and annotations produced by Desktop for field parameters? Asking because field parameters work fine with PBIP and Git Integration when created from Desktop, if you do exactly the same manually it should work fine.Yes, the power bi file with the manually implemented field parameter works fine in power bi desktop and in the service. The only difference I can see between this and one generated by Power BI desktop is that the power bi desktop field parameter table is manually created and mine has a SQL query as a source because it comes from a table in snowflake. Mine does also have one additional column with a second sort value.