Skip to main content

Notifications

Microsoft Dynamics SL (Archived)

Installing Updates Causes Loss of Access to Reports

Posted on by Microsoft Employee

After installing updates to Dynamics SL 2011 we have experienced a situation where we are not able to access custom reports through the ROI.  Thru necessity or ignorance we end up resetting the RPTCONTROL table (and maybe another table) back to default.  Once it is restored everything is fine again, but should this be a part of a feature pack install process?  Or are we doing something in error.  Our reseller and Microsoft have both apparently indicated this is expected behavior, but I have a hard time believing that.

Thanks,

Alan

*This post is locked for comments

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Installing Updates Causes Loss of Access to Reports

    Hi

    During Database Maintenance update the  RptControl and Pvrec tables under the Solomon system database will be get overridden with standard values. This will  impact your custom reports and pvrec execution. To avoid this we need to take a backup of both tables before  Database maintenance update and restore it after the upgrade process.

    Hope this helps

    Thanks

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Installing Updates Causes Loss of Access to Reports

    Your reseller is correct if the report control customizations are to standard SL report controls.  The database update (under database maintenance) process clears out the report control table for all standard SL modules and when you run the database update process under Administration to put in the standard report controls you are at the level of report controls that are standard with the version of SL you just installed.

    What you did will bring back your customized report controls but will also lose and changes to report controls that came with the new SL update.  Sometimes that can even cause a report to fail under the new release because the new release may have changed where it pulled something like the current posting period so your approach may result is some ROI errors when you attempt to launch a report.  This is not a high probability but you need to be aware of it.

    Before I do any SL update I always use SQL to copy the rptcontrol table to another table name in the system database so that I still have my customized report controls.  I can then cut and paste in (from the alternate rptcontrol table) the custom report control changes that were made.  Not exactly an easy task but better than losing customized controls.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,240 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,149 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans