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.
Hi,
We are starting to implement a more "professional" approach to our current PBI development activities and one of the must to have requriements is to impleement a version control system that might be integrated with Azure/DEVOPS and power bi pipelines.
I have been considering 2 options:
- Tabular editor (versio 2 or 3)
- pbi-tool
Both them seems to match our requirements. That is:
- Convert pbix file onto json files that might be managed on a VCS (tabular folder structure vs pib-tools folder structure)
- Integration with Azure DEVOPS repository
Based on your experience, which tool would best fit this requirement?
Thanks,
Alfons
Hi @alfBI,
Both Tabular Editor and pbi-tools can help you manage your Power BI development artifacts with a version control system and integrate with Azure DevOps. However, there are some differences between the two tools that you should consider when deciding which one to use.
Tabular Editor is a powerful tool for authoring and managing Tabular models, including Power BI models. It can convert PBIX files to Tabular Object Model (TOM) JSON files, which can be managed with a version control system. Tabular Editor also has built-in integration with Azure DevOps, which allows you to commit changes to a Git repository and create pull requests directly from the tool.
Pbi-tools is a command-line tool that can extract Power BI reports and datasets from PBIX files and convert them to JSON files. It also provides a folder structure for managing these files with a version control system. Pbi-tools can be used with any version control system, including Git, and can be integrated with Azure DevOps using the Azure DevOps command-line interface (CLI).
The choice between Tabular Editor and pbi-tools depends on your specific needs and preferences. If you need a powerful tool for managing Tabular models in addition to Power BI reports, Tabular Editor may be the better choice. If you prefer a lightweight command-line tool that can be used with any version control system, pbi-tools may be a better fit.
In general, both tools can help you manage your Power BI development artifacts with version control and integrate with Azure DevOps, so you should evaluate each one and choose the one that best fits your needs.
In my personal experience, I would choose Tabular Editor, as I have already seen the implementation at an organizational level in a large tenant with a large base of users (Thousands). However, as mentioned before, it will depend on your specific needs.
Best regards,
Isaac Chavarria
If this post helps, then please consider Accepting it as the solution and give Kudos to help the other members find it more quickly
Hi Isaac,
Thanks for your answer. Effectively Tabular Editor looks like a more robust tool, well suited for enterprise level but I am not sure it can fulfill the whole scenario (version models & thin reports).
TE is fine to implement control version on PBI models but not for thin-reports (fix me if I am wrong). In this case we would need to use pbi-tools or a less robust approach (Sharepoint)
How do you prefer to version thin-reports?
Alfons
Hello @alfBI
What is your feedback on bvest tool to implement source control version between pbi-tools vs tabular editor ?
Best regards
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.
User | Count |
---|---|
12 | |
2 | |
1 | |
1 | |
1 |