Mar 18, 2015

Management Reporter 2012 - How to Delete Report Queue Manually?

All the Report Process are stored in the Management Report Database under the table "Repository".
To manually remove reports that are stuck in Queue status, use the below SQL scripts.
  1. Log in to SQL Management Studio with admin privilege.

  2. Run the below script against Management Reporter Database

    USE ManagementReporter
    -- View the Records
    Select * from repository where StatusType = 30
    or
    Select * from repository where StatusType = 30 and Name '<Report Name>'

    -- Delete the Records
    Delete Repository where StatusType = 30 and Name '<Report Name>'

  3. Open Management Reporter and Check if this has cleared all the Report Queue.
    Tools >> Report Queue Status.

Mar 1, 2015

Post GP Upgrade Checklist

Validate Upgrade Completion:
  • Ensure that the upgrade process has completed successfully without any errors or interruptions.
  • Verify that all necessary components of Dynamics GP, including databases, modules, and customizations, have been upgraded to the desired version.
Backup Data and Configuration:
  • Perform a comprehensive backup of all Dynamics GP databases, configurations, and customizations.
  • Store backups in a secure location to ensure data integrity and facilitate restoration if needed.
Test Functionality:
  • Conduct thorough testing of Dynamics GP functionality to ensure that all modules and features are working as expected in the upgraded version.
  • Test core processes such as financial transactions, inventory management, sales, purchasing, and reporting.
Verify Customizations and Integrations:
  • Validate that any customizations, integrations, or third-party add-ons are compatible with the upgraded version of Dynamics GP.
  • Test custom reports, workflows, scripts, and any other tailored functionalities to confirm their continued functionality.
Review Security Settings:
  • Review and update user roles, permissions, and security settings as necessary.
  • Ensure that security configurations are aligned with organizational requirements and compliance standards.
Check Data Integrity:
  • Perform data integrity checks to identify and resolve any inconsistencies or discrepancies in the upgraded data.
  • Utilize built-in tools or scripts to verify data integrity across all modules and databases.
User Training and Communication:
  • Provide training sessions or documentation to familiarize users with any changes or new features introduced in the upgraded version.
  • Communicate effectively with stakeholders about the upgrade process, including timelines, expected downtime, and potential impacts on workflows.
Performance Tuning:
  • Monitor system performance after the upgrade to identify any bottlenecks or issues.
  • Implement performance tuning strategies such as database optimization, indexing, and configuration adjustments to enhance system responsiveness.
Documentation and Reporting:
  • Document the upgrade process, including steps taken, issues encountered, and resolutions applied.
  • Generate post-upgrade reports to track key metrics such as system performance, user feedback, and adherence to project timelines.
Continuous Monitoring and Support:
  • Establish ongoing monitoring procedures to detect and address any post-upgrade issues proactively.
  • Provide dedicated support channels for users to report any issues or concerns related to the upgraded Dynamics GP environment.
        By following this checklist, you can ensure a smooth transition and maximize the benefits of your Dynamics GP upgrade while minimizing disruptions to your organization's operations.