Forum Discussion
Version control
Are they going to be working on the same semantic model? or they will be creating their own reports and semantic model? The approach will be different. However, here is a good place to start.
https://learn.microsoft.com/en-us/fabric/cicd/git-integration/git-get-started?tabs=azure-devops%2CAzure%2Ccommit-to-git
Can you elaborate what "collaboration among developers in different department" in your use case?
As far as i know, P1 doesnt limit collaboration. You can still use azure devops, branching etc. and leverage pbip and version control in git repo. What are the limitations that you are encountering?
Also, sooner or later you will need to move to F-sku, as P-sku is not being offered anymore. Once your current P sku contract ends, you can only continue on F sku.
Do you have a guide or documentation I can follow? I haven't used Azure DevOps or branching before, but I'm interested in trying it out.
"collaboration among developers in different department" means , We need to collaborate with developers from different departments located in various regions.Are they going to be working on the same semantic model? or they will be creating their own reports and semantic model? The approach will be different. However, here is a good place to start.
https://learn.microsoft.com/en-us/fabric/cicd/git-integration/git-get-started?tabs=azure-devops%2CAzure%2Ccommit-to-gitTutu_in_YYC We are working on the same semantic model. THanks for the document,but this document is for fabric users. Our organization operates under a Microsoft P1 license, without access to Fabric. And we dont have the workspace setting option to continue.
