Forum Discussion
Paginated Report development cycle - using the Service with Report Builder and multiple sub-reports
#1 - it's all you. Get your repository, clone it, push the changes etc. Nothing is built in.
#2 - We've been asking for this for a while. Maybe it will come some day. In the meantime ALM Toolkit and Deployment Pipelines are some (weaker) stop gap alternatives.
Keep in mind that RDL files are XML with a weird file extension. You can ingest them in git directly. PBIX (or better PBIT) are ZIP files that you first need to extract, and then you have a bunch of JSON.
#1 - it's all you. Get your repository, clone it, push the changes etc. Nothing is built in.
#2 - We've been asking for this for a while. Maybe it will come some day. In the meantime ALM Toolkit and Deployment Pipelines are some (weaker) stop gap alternatives.
Keep in mind that RDL files are XML with a weird file extension. You can ingest them in git directly. PBIX (or better PBIT) are ZIP files that you first need to extract, and then you have a bunch of JSON.
As a solo developer, my ALM needs are well served with simple versioning + replication to the cloud. I have never used GitHub or other source code management system. Protecting my PBIX, RDL and earlier ASP.NET assets was all I needed. My third and final question is simple, perhaps naive, and maybe bordering on dumb, but why would I "ingest" them into git? To my mind, "ingest" means more than "copy to", and your reference to JSON and ZIP does not seem to apply to my need to protect intact PBIX and RDL files. What will git do for me beyond archiving and versioning my files? (yeah, making you earn your kudos today, let's make it three + Solved! and call it a day)