Sage CRM 2022 R1 release, learn new features and improvements executed in the Sage CRM 2022 R1 update. It is expected for Sage CRM accomplices, Sage OpCos, and Sage CRM clients.
Contingent upon the location you are in, you can get permit keys for this Sage CRM 2022 R1 release to install explicit item modules like Sales, Service and Marketing (or blends of these modules). For more data on the accessibility of modules and the arrangements accessible in your area, if it’s not too much trouble, contact Sage experts Team.
While installing the release Sage CRM 2022 R1, you can alternatively choose to send unknown Sage CRM use insights to Sage throughout Google Analytics. This data will permit Sage to work on the administrations and programming we give to our clients.
Sage CRM 2022 R1 release date and Files included
Release date:
January 2022
Documents included:
- eWare.dll (Version 20.22.0.1)
- Viewpoint module (Version 20.22.0.1)
- Record module (Version 20.22.0.1)
Documentation and help
To see setting touchy assistance, click on the Help key in Sage CRM 2022 R1.
For more data about the product with which Sage CRM 2022 R1 can work and incorporate, see the 2022 R1 Hardware and Software Requirements posted on the Sage CRM Help Center.
For online User Help, online System Administrator Help, and all PDF documentation for this delivery, go to the Sage CRM Help Center.
Note: Translated guides and help have been ceased. Just English documentation is currently provided with Sage CRM.
Sage CRM 2022 R1 New Features and Improvement
Know what’s new in Sage CRM 2022 R1 gives the accompanying new features and improvements:
1. Store Sage CRM information in Azure SQL Database
The Sage CRM Setup gives another choice Connect to a Microsoft Azure SQL arrangement. While playing out another Sage CRM introduce, you can utilize this new choice to associate with a Microsoft Azure SQL Database server, make another information base, and store Sage CRM information in it.
Sage CRM upholds the accompanying Azure SQL arrangements and asset types:
Upheld arrangement: Microsoft Azure SQL Database
Upheld asset type: Database server
Prior to running the Sage CRM Setup, ensure that the objective Azure SQL Database server exists.
To make another Azure SQL Database server viable with Sage CRM:
1. Go to https://portal.azure.com/#create/Microsoft.AzureSQL.
2. Under SQL data sets, from the Resource type list, select Database server.
3. Select Create and follow the means to make another Azure SQL Database server.
Right now Sage CRM doesn’t uphold some other Azure SQL arrangements and asset types.
Think about the accompanying impediments:
You can’t utilize the Sage CRM Setup to choose a current information base in Azure SQL. Right now, the Setup can make another information base on a current Azure SQL Database server.
Sage CRM Setup can’t relocate information from a current on-premise Microsoft SQL Server data set to Microsoft Azure SQL.
For more data about Microsoft Azure SQL Database, see What is Azure SQL Database?.
For a total rundown of upheld data set programming, see the Sage CRM 2022 R1 Hardware and Software Requirements distributed on the Sage CRM Help Center.
Also Read: Install Sage 50 Connection Manager on Server
2. Search specific element utilizing RESTful API
In the RESTful API provided with this delivery, another discretionary element boundary is accessible for the Search elements utilizing Quick Find endpoint. You can utilize the element boundary to limit your Quick Find search to a solitary substance.
The substance boundary upholds similar norm and custom elements as Quick Find, it can take one of the accompanying qualities:
- Company
- Individual
- Opportunity
- Lead
- Correspondence
- Orders
- Quotes
- Cases
- Arrangements
- Library
- Custom substance name
The boundary values are case delicate, enter them precisely as displayed previously. While indicating a custom substance name, enter it precisely as it shows up in the Sage CRM UI.
To perceive how the element boundary functions, you can utilize the Sage CRM 2022 R1 Postman assortment. It contains an example demand telling the best way to look through organizations.
To utilize the solicitation, import the assortment and climate documents into Postman, grow the RESTful API endponts (previously SData) organizer in the assortment and utilize the Search organizations utilizing Quick Find demand.
Example request
curl – – request GET http://127.0.0.1/sdata/crmj/sagecrm2/$service/quickFind/getResults?query=eurolandia&SID=XXXXXXXXXXXXXXX&entity=Company
This solicitation looks for organizations (entity=Company) whose single-line text, email address, or URL field contains the word eurolandia (query=eurolandia). The SID boundary contains the meeting ID of the Sage CRM client who sends the solicitation.
3. Mass delete communications
Feature ID: CRMS-696
To further develop framework execution, you can lessen the size of the Sage CRM data set by mass erasing the correspondence records clients never again need.
Whenever you do as such, Sage CRM plays out a hard erase on the correspondence records. This implies the records get forever erased from the Sage CRM data set and the best way to recuperate them is to reestablish the data set from a reinforcement.
1. Back up the Sage CRM information base.
- This is expected on the off chance that you need to reestablish the correspondence records you are going to erase.
2. Go to | Administration | Data Management | Hard Delete Communications.
3. In Delete all correspondence records last refreshed previously, select a date.
4. Set the accompanying choices to Yes:
- I have supported the Sage CRM information base.
- I comprehend that the cancellation is extremely durable.
5. Select Delete.
6. When provoked, affirm that you need to forever erase the correspondence records.
Note: If Sage CRM experiences a mistake while mass erasing interchanges, it rolls back the progressions previously made and leaves your framework in salvageable shape.
4. Change default location of log files
Feature ID: CRMS-633
The System Administrator Help has been refreshed to give guidelines on the most proficient method to store Sage CRM log documents in an alternate envelope.
As a matter of course, Sage CRM stores its log documents in %ProgramFiles(x86)%\Sage\CRM\CRM\Logs. Framework chairmen can utilize the mklink apparatus given by Microsoft to make a registry intersection for this organizer and whatever other envelope where they need to store the log records.
Note: These means are relevant provided that your Sage CRM server utilizes NTFS.
1. On your Sage CRM server, physically make another envelope for putting away Sage CRM log documents. For instance:
C:\new-logs-area
2. Stop IIS: at a comand brief, run iisreset/stop.
3. Rename the current envelope putting away the log records, for instance:
C:\Program Files (x86)\Sage\CRM\CRM\Logs-reinforcement
4. Open the Command Prompt window as chairman.
5. Make a registry intersection for the first log records envelope and the new organizer, for instance:
mklink /J “C:\Program Files (x86)\Sage\CRM\CRM\Logs” C:\new-logs-location
6. Start IIS: at an order brief, run iisreset/start.
7. Check the new log records area to ensure IIS has made the log documents there. Assuming this is the case, erase the renamed log records organizer (C:\Program Files (x86)\Sage\CRM\CRM\Logs-reinforcement).
5. Update territory on all leads, cases, or opportunities in group
Feature ID: CRMS-370, CRMS-473
Framework overseers can refresh an area on bunches containing leads, cases, or amazing open doors. To do as such, open a gathering and select Update Territory under Actions.
Also Read: Sage Education
6. No changes allowed to users sharing one email address
Feature ID: CRMS-717
Sage CRM broadens the necessity for every client to have a remarkable email address to circumstances where a framework chairman or data administrator alters a current client.
Presently in the event that a client being altered offers a similar email address with another client, the framework director or data administrator can’t save their progressions until they allot a remarkable email address to the client.
Framework overseers can in any case move up to Sage CRM 2022 R1 from a previous Sage CRM variant where a few clients share a similar email address. Such clients will continue to have a similar email address in 2022 R1 in the wake of updating. You can relegate novel email locations to such clients at whatever point helpful for you.
Note: We firmly suggest that every Sage CRM client in your current circumstance has a one of a kind email address alloted. By allocating extraordinary email addresses, you can keep away from expected issues. For instance, where some unacceptable client gets an email message that is expected for an alternate client.
7. Insert email signature into replies and forwards
Feature ID: CRMS-726
While making or altering an email signature, you can utilize another check box Use signature for answers and advances.
Select this really take a look at box to embed your email signature into new messages and while answering to or sending messages. At the point when you clear this check box, your email mark is embedded into new messages as it were.
For more data on the most proficient method to make or alter an email signature, see Managing your email signature in the User Help
8. Resize table columns in email templates
While embedding or altering a table in an email layout in | Administration | Email and Documents | Email Templates, framework managers can resize the width of the table sections.
To do as such, float over the boundary of the table segment you need to resize. Whenever the pointer turns into a twofold headed bolt ( ), snap and drag the boundary to resize the section width.
9. Automatically refresh calendar and calendar list
Feature ID: CRMS-511
You can utilize another choice Calendar invigorate stretch in | Administration | System | System Behavior to set the programmed revive rate in seconds for the Calendar and Calendar List tabs. To debilitate invigorate, set this worth to a clear worth or 0.
10. Display version and license key information
Sage CRM overseers can show or conceal data about the introduced Sage CRM adaptation, permit key, and form support end date. This data is shown at the highest point of the screen in the | Administration region.
To show or conceal the data, directors can utilize another field Show form and permit information in | Administration | Preferences. As a matter of course, this field is set to Yes.
Note: To recover and show data about at present upheld variants, Sage CRM requires an Internet association. On the off chance that your Sage CRM server isn’t associated with the Internet, we suggest that you set Show form and permit information to No.
11. Help for new programming
Microsoft SQL Server 2019 Express: This SQL Server form is presently appropriated in the Sage CRM establishment bundle. You can introduce and utilize Microsoft SQL Server 2019 Express along with another establishment of Sage CRM. At the point when you update from a past Sage CRM rendition that utilizes a more seasoned SQL Server Express form, Sage CRM Setup keeps the introduced SQL Server Express form.
Microsoft Azure SQL Database: While playing out another establishment of Sage CRM, framework directors can interface with a Microsoft Azure SQL Database arrangement, so the Sage CRM Setup makes another data set and stores Sage CRM information there. For subtleties, see Store Sage CRM information in Azure SQL Database in this report.
Windows 11: Clients can get to Sage CRM from client PCs running Windows 11.
Discontinued features
Help for Microsoft Internet Explorer 11: Sage CRM has quit supporting Microsoft Internet Explorer 11 in front of the program’s retirement by Microsoft on 15 June 2022.
Along with Internet Explorer 11, the accompanying Sage CRM highlights have been suspended in light of the fact that they are not accessible in different programs upheld by Sage CRM:
- Alter consolidated reports
- Send messages utilizing Outlook
Print the intuitive dashboard (feature ID: CRMS-425, CRMS-530). We have taken out the Print order from the upper right corner of the intuitive dashboard. Your internet browser might have a print highlight that can print the dashboard.
Installing and upgrading
Note: Install just a single Sage CRM case per server. Sage doesn’t uphold arrangements where at least two Sage CRM cases are introduced on a similar server.
Installation requirements
Prior to introducing or overhauling Sage CRM, ensure that:
- Your current circumstance meets the Sage CRM 2022 R1 Hardware and Software Requirements distributed on the Sage CRM Help Center.
- You have Microsoft OLE DB Driver 18 for SQL Server introduced on the SQL Server that will have the Sage CRM information base.
Download Microsoft OLE DB Driver 18 for SQL Server
On the off chance that you don’t have this driver introduced, the Sage CRM Setup can’t associate with the SQL Server.
Upgrade path
You can utilize the Sage CRM 2022 R1 establishment bundle to overhaul from renditions 2021 R2, 2021 R1, 2020 R2, 2020 R1, 2019 R2, and 2019 R1.
To upgrade from a previous variant of Sage CRM, kindly first move up to one of the adaptations recorded here.
Note: Computer communication coordination (CTI) has been eliminated from Sage CRM 2022 R1 and is not generally upheld. Assuming you have CTI introduced in a past Sage CRM variant, moving up to 2022 R1 totally eliminates CTI.
Post-installation/upgrade tasks
Sage CRM Setup can’t overhaul Microsoft SQL Server Express introduced with a past Sage CRM rendition. Subsequently, you might wind up with Sage CRM utilizing an unsupported Microsoft SQL Server Express form. In the event that important, physically update Microsoft SQL Server Express in the wake of redesigning Sage CRM.
For upheld Microsoft SQL Server Express forms, see Sage CRM 2022 R1 Hardware and Software Requirements distributed on the Sage CRM Help Center.
Ensure that client passwords in Sage CRM are not clear. We test Sage CRM highlights in a climate where each client has a nonblank secret word allocated. In the event that you have clear client passwords in your current circumstance, Sage CRM elements might act unusually.
Sign on to Sage CRM as a framework head to some degree once prior to moving up to the following variant. This is expected to refresh the Sage CRM information base accurately.
Clear the Web program store on every client’s PC to guarantee the Interactive Dashboard works accurately
Reemerge the Sage CRM framework head secret key after you have updated Sage CRM that is incorporated with another framework. This is expected to hash and safely store the secret phrase.
- Sign on to Sage CRM as a framework overseer.
- Go to | Administration | Integration | Integration List and snap the coordination for which you need to reemerge the secret key.
- Select Disable and afterward select Continue.
- Select Change.
- In the CRM Password text box, return the secret key.
- Select Save.
- Select Enable.
Note: You should reappear the Sage CRM framework director secret key utilizing the means above at whatever point you adjust your incorporation.
Get in touch
Here you learned New features and improvement of Sage CRM 2022 R1 Release. Still Do you have any Question or need assistant? You can contact sage experts team via Phone Call, Email at: info@accountscomparison.com or you can also do Live Chat with our sage experts they will provide solutions for you query.