Addressed issues
The following is a list of customer cases addressed in this release.
Issue ID |
Area |
Description |
Status |
---|---|---|---|
CRMS-694 |
Cases, |
In some scenarios, a workflow that created a Communication (for example, sent an email about a raised case to several users) added more than one record into the Communication database table for that Communication. The expected result is that each Communication should have only one record in the Communication database table. If an email was sent to several users, the workflow should create multiple records in the Comm_Link database table and link them to the single record in the Communication table. |
Fixed |
CRMS-1435 |
Cases, |
In some scenarios, a field value set by a workflow action was unexpectedly truncated to 10 characters. This issue occurred when a workflow action was configured to reset a value in a column and replace it with the value from a field whose Attribute was set to Hidden. |
Fixed |
CRMS-1409 |
Companies, |
When a user opened a Company that had no default Person assigned, the contact information for the Company was empty. |
Fixed |
CRMS-1405, |
Companies, |
When you edited a Company record that didn’t have a primary contact assigned, the following error occurred: “An unexpected event has occurred: Exception: Error – Record not found, you may not have security permissions.” |
Fixed |
CRMS-1370, |
Core product |
When using Google Chrome version 113.0.5682.64, every time you selected a clickable user interface element in Sage CRM, a Leave site? pop-up message appeared. |
Fixed |
CRMS-915 |
Customization |
In some scenarios, a report provided the wrong ID of a custom entity record. For example, this issue occurred when you completed the following steps:
As a result, when you ran the report and selected the ID of a custom entity record there, the wrong custom entity record opened. |
Fixed |
CRMS-742 |
Customization |
The options available under Desktop HTML list contents were different in situations where they should be identical. This issue occurred when you did the following:
The options displayed in steps 1 and 2 were different, whereas they should be identical. |
Fixed |
CRMS-1424 |
Customization, |
It was not possible to add Lead fields to the Lead grid because no Lead fields were available. In particular, this issue occurred when a system administrator performed these steps:
As a result, the Lead fields were missing from the Field list. |
Fixed |
CRMS-1454 |
Customization, |
It was not possible to customize the Opportunity grid because no Opportunity fields were available. In particular, this issue occurred when a system administrator performed these steps:
As a result, the Field list was empty. |
Fixed |
CRMS-1372 |
Dashboard |
The filter options (such as Filter by) were missing from the dashboard gadgets on which filters were supposed to be available. For example, this issue affected the My Open Opportunities gadget. |
Fixed |
CRMS-1460 |
Documentation |
The documentation used the old name of Microsoft Entra ID: Azure Active Directory. |
Fixed |
CRMS-1884 |
Documentation |
The instructions on how to configure OAuth 2.0 for Exchange Online used the old name of Microsoft Entra ID: Microsoft Azure Active Directory. |
Fixed |
CRMS-1378 |
|
Sage CRM stopped responding when a user selected a workflow action that sent an email message containing an attachment. This issue affected only those users whose name contained non-English characters. |
Fixed |
CRMS-1414, |
|
The Font and Size options were missing from the embedded email editor. |
Fixed |
CRMS-1089 |
|
When a user forwarded an email using the embedded email editor, the aspect ratio of the images was lost and the images were distorted after the email arrived into the recipent's inbox. |
Fixed |
CRMS-1188 |
|
When Email Management Server Options in |
Fixed |
CRMS-1199 |
Email, |
When an OAuth 2.0 token used to access an Outlook mailbox in Microsoft Office 365 expired, Sage CRM wrote the following misleading error to the log: "Exception connecting to Mail Server: Authentication failure: unknown user name or bad password." |
Fixed The message written to theSage CRM log has been changed to describe the issue correctly. |
CRMS-970 |
Lite Outlook plugin |
After a user filed an email with an attachment whose name contained Chinese characters, these characters were replaced with blank spaces. |
Fixed The Lite Outlook Plugin has been replaced with the Enhanced Email Import feature in Sage CRM 2022 R2 and later. Use this feature to import emails containing attachments with Chinese characters. For more information, see Importing contacts and email messages from Exchange Online. |
CRMS-1244 |
Mail merge |
When a workflow action that ran a mail merge was configured to create a .docx document, it erroneously created a .doc document. |
Fixed |
CRMS-1447 |
Mail merge |
When a user performed a mail merge and edited the merged file, the file was not attached to the target record in Sage CRM. This issue occurred only if a user did the following during mail merge:
|
Fixed |
CRMS-1043 |
Opportunities |
When you viewed an Opportunity record, the top section of the record showed the details of a different Opportunity. This issue occurred in the following scenario:
|
Fixed |
CRMS-1233 |
Opportunities |
You encountered “An unexpected event has occurred” error when you did the following:
|
Fixed |
CRMS-1384 |
Opportunities |
When a user selected a stage in the Opportunity pipeline, several stages were selected. |
Fixed |
CRMS-1251 |
Opportunities |
When a user selected an Opportunity in Team CRM | Opportunities, and then selected the Orders tab, no Orders were displayed. |
Fixed |
CRMS-1260 |
Opportunities |
When a user opened an Opportunity in Team CRM | Opportunities, selected the Orders tab, and then selected the Summary tab, the following error occurred: "Cannot create quotes and orders because current opportunity has items." |
Fixed |
CRMS-1419 |
Opportunities |
In some cases, the Opportunity pipeline showed the incorrect name of one or several stages and the wrong number of records in a stage. This issue occurred when a system administrator customized the Opportunity pipeline by adding new stages. |
Fixed |
CRMS-1361 |
Opportunities |
When a user tried to edit an Opportunity by going to Team CRM | Opportunities and selecting an Opportunity, the following error was displayed: "An unexpected event has occurred: Exception: Error - Record not found, you may not have security permission." |
Fixed |
CRMS-1345 |
Opportunities |
When a user tried to modify an Opportunity record, the following error displayed: “An unexpected event has occurred. Exception error – record not found, you may not have security permissions.” This issue occurred after the system administrator customized Sage CRM to add a field from the Opportunity database table to the Case Details screen. |
Fixed |
CRMS-1223 |
Opportunities, |
In some scenarios, when you opened an Opportunity in Team CRM | Opportunities, and then selected the Quotes tab, the New button was missing and it wasn't possible to create a new Quote. |
Fixed |
CRMS-1194 |
Opportunities, |
After upgrading Sage CRM, an Opportunity-related workflow stopped working. For example, when a workflow was configured to assign a review team to a newly-created Opportunity, it did not happen. |
Fixed |
CRMS-868, |
Quick find |
A company name containing parentheses was displayed incorrectly in Quick Find. For example, the name part inside the parentheses was displayed as undefined. |
Fixed |
CRMS-1033 |
Self service |
The following error occurred in the Self Service UI: “eWare.eWareBlockContainer error `<error code>`[SafeCall Exception]: Catastrophic failure” |
Fixed |
CRMS-1387 |
Web services |
When a system administrator scanned their Sage CRM server using ManageEngine Vulnerability Manager Plus, they observed the following vulnerabilites caused by Tomcat 9.0 supplied with Sage CRM: |
Fixed Tomcat supplied with Sage CRM has been updated to version 9.0.75, where these vulnerabilities are addressed. |
CRMS-1300 |
Workflow |
The following issue occurred when a system administrator edited a workflow in When the Available Rules list was long (30+ rules), it was not possible to drag a rule from the bottom of the list to the desired part of the workflow diagram, because the diagram wasn't scrollable. |
Fixed |