Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hit Reply to tell us about your experience with Power BI Project files (PBIP) and Fabric Git Integration for Power BI Semantic Models and Reports so we can continue to improve.
For example:
Thanks,
-Power BI team
LocalDateTable entry are an indication that you forgot to disable Auto Date/Time. They should never be part of an enterprise semantic model.
Hi
We have a lot of reports connected live to on-prem ssas (Fabric is on the road map)
I would like to add the report-part of these files into source control, and I think I succeded with it yesterday.
I save the thin report as pbip > commit to devops repo > connect from workspace to repo.
But trying the setup from scatch again today, when I click on Update all in the workspace I just get: Failed to discover dependencies ... Azure Analysis Services and SQL Server Analysis Services hosted semantic models are not supported....
Is it possible?
We are working to support the AS/AAS scenario. Until then of all you want to source control the thin reports, if you live connect the report to the model in the service and not to Analsysis Services it should work because the connection in definition.pbir will be to the model in the workspace and not to Analysis Services. I believe the error you get its because the connection in definition.pbir is to the Analysis Services server. Can you confirm?
Great that you are working on it.
Yes, I can confirm. There is no model in the service, I can connect to, as the reports are connected through a gateway to on-prem SSAS. So I have saved the AS connected PBIX as a PBIP, and get the error when I try to sync from Azure DevOps repo into an empty workspace. The definition.pbir connectionString is pointing at the SSAS server.
Please allow an option for more granular serialization to represent measures as distinct TMDL files rather than part of a larger table definition. This makes maintaining measures simpler.
I currently do this with TE3 folder structure in JSON format and can't switch to TMDL until this level of granularity is possible.
Its in our backlog, but not a priority. Can you please log a new idea on aka.ms/fabricideas?
Hi @RuiRomanoMS ,
What changes would you like to see?
I hope the UI interface is more concise and clear, and the synchronization of Git integration can be more real-time and convenient
What are your main challenges/issues?
The synchronization steps of Git integration are a bit cumbersome, and sometimes there are some restrictions
Any suggestions for additional settings or capabilities?
I hope to broaden the compatibility and support for synchronization of certain unsupported workspace items (especially fabric-related items).
Best Regards,
Liu Yang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
4 | |
3 | |
2 | |
2 | |
2 |