Sage CRM 2022 R1: Changes to the database and metadata

1 minute read time.

Sage CRM 2022 R1 has now been released from the development team. The exact release date in your country will be determined by your local Sage team as the final processes go to market preparations will need to be confirmed.

Each release has a different focus within the overall roadmap. The changes in Sage 2022 R1 have largely been focused on improvements to the experience in Deployment and Administration.

We've delivered in this release several new features that depend on changes to metadata and to the data model. These include

  • Support for Azure SQL database
  • REST API improvements
  • Mass delete of historic communications
  • The ability to Change default log locations
  • Update territory on Leads, Cases, or Opportunities
  • Additional data integrity rules – no changes to users sharing one email address
  • Insert signature in replies and forwards
  • Resizable table columns in the email (HTML) templates
  • Auto-refresh of Calendar and Calendar List
  • Display of version and license key information

Understanding the changes to the metadata and data model is important for customers planning to upgrade their system from an earlier version.

Upgrading may impact

  • Integration with account systems
  • Existing Customizations
  • Database tables and views
  • Metadata.

As part of the preparation for an upgrade, we need to make sure that all the resources that are needed are assembled.

The Sage CRM Community has additional resources to help partners. These include a spreadsheet that lists the main metadata and database changes that have been made between Sage CRM 2021 R2 and Sage CRM 2022 R1. You can download this from the Example Downloads and Components folder.

https://community.sagecrm.com/partner_community/m/example_components__developer_resources/default.aspx

It covers in detail

  • What Columns have been added to Existing Tables
  • System Parameters added to the system
  • New Captions

We do not anticipate these changes causing an issue for an upgrade.

Make sure that when preparing a system to be upgraded you use all the resources provided.