Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested answer

How can I update a SSRS report without applying a deployable package to production?

(2) ShareShare
ReportReport
Posted on by 64
Hello community,

I need to update an SSRS report in a production environment without deploying a full deployable package. My repository contains multiple changes that are currently applied in test environments like UAT/FUT, but these changes are not ready for production yet. I only want to apply the specific SSRS report change to production without including the other changes in the repository.

Is there a way to update the report directly in production ? What is the best practice for handling such scenarios?

Thanks in advance!

 

Mario C.

Categories:
  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 231,307 Most Valuable Professional on at
    How can I update a SSRS report without applying a deployable package to production?
    You can't deploy your changes without deploying them, but your problem is different anyway. You have a problem with your branching and deployment strategy.

    You seem to believe that you deploy code from environments, but it isn't the case. T2+ environments don't even contain code that you could create a deployable package from. A deployable package should be created from a known version in source control, not from something that happen to be in an environment. And in source control, you have branches for this purpose.
     
    What you have in production may be code stored in a production branch, or (for instance) an older version of a main branch. Depending on your situation, you can cherry-pick individual changes for merge to the production branch, create a new branch from an older version or so. Then you'll use a pipeline to create a deployable package from that branch, you'll apply it to a test environment, test it and then deploy your changes to production. If you develop changes in other branch then where you usually develop, you'll also need to merge the changes there. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,494 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,307 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans