Let the platform do the work

Sugar Enterprise 13.0.1 Release Notes


This document describes the changes and functionality available in Sugar® Enterprise 13.0.1. Sugar 13.0.1 is available for customers on the annual upgrade path. For customers upgrading from 12.0.3, please refer to the Sugar 13.0 (Q2 2023) release notes for additional features, fixed issues, and developer changes occurring between versions 12.0.3 and 13.0.1.

Note: This release is not available for SugarCloud customers.

Fixed Issues

The following issues are resolved in this release. Case portal users can use the following links for more details about each issue:

  • 92592: Upgrades to Sugar may fail in certain circumstances.
  • 92418: When accessing Sugar using the Chrome browser on an iPad, the fields and user interface elements may not display properly as expected in the module's record view (e.g., Leads). 
  • 92342: For instances containing a large number of contacts and accounts, users may experience unexpected performance issues with adding recipients in the To field when composing emails in Sugar. 

Known Issues

Click the link below to expand or collapse the 13.0.1 known issues list.  

The following known issues are present in this release. Case Portal users can use the following links for more details about each issue: 

  • 92005: For Sugar 12.3 instances with a modified Advanced Search layout in the Users module, upgrading to Sugar 13.0 results in unexpected issues for the Users module's search functionality.
  • 91146: Doc merging records using a template containing custom fields may fail to generate with an error. 
  • 91023: The Search and Select Users drawer may not display the correct count of user records if there is an inactive user in the instance. 
  • 91003: When a report fails to run due to a 500 error, the error message that appears should be more meaninful and informative.
  • 90866: In certain circumstances, replying to an email in Sugar may fail to send and result in a 500 error. As a workaround, click the To field in the email to display the To and From field values first before sending the email.   
  • 90847, 88858: Unexpected email issues may occur in Sugar when using the Microsoft Exchange mail account as the authorized system email account.  
  • 90615: When logged into Sugar using a non-English language (e.g., French), changing the classification value for the sales_stage_dom list in Admin > Dropdown Editor may improperly change the classification values for the other list items. As a workaround, log in to Sugar with the English (US) language and manually update the classification of the list items to the correct values. 
  • 90322: Certain languages (e.g., Chinese, Japanese) with special characters display incorrectly in reports exported as a PDF or CSV file. 
  • 90059: In certain circumstances, sorting a related-record subpanel (e.g., Leads) using the Account Name field column may result in an unexpected error. As a workaround, sort the subpanel using a different field column to stop the error and allow the subpanel to load. 
  • 89878: The Forecast Bar Chart dashlet in the Forecasts module does not display any data for individual sellers. 
  • 89831: Exported reports do not respect the locale settings in Sugar and incorrectly displays the date using the YYYY-MM-DD format. 
  • 89728: In certain circumstances, opening the list view Mass Actions menu does not display properly on the screen. 
  • 89641: Hint-related error messages are logged for some recently upgraded Sugar 12.0 instances that do not have Sugar Hint.
  • 89542: For instances wth a very large number of SugarBPM processes, trying to view the list of processes in the Process Management's list view may result in performance issues and fail to load. 
  • 89525: Selecting "All" from a record's related subpanel filter does not get preserved and reverts back to the last option chosen when logging out of Sugar.
  • 88957: In certain circumstances, performing a global search in Sugar may result in a 500 error.  
  • 88374: Attempting to reorder the columns in the Worksheet Columns Preview list view in Admin > Quotes Configuration does not work as expected. As a workaround, remove all the fields from the Worksheet Columns section then add the fields again to the section. 
  • 88366: When performing an advanced search in legacy modules (e.g., Users), the Status field may default to "NULL" causing search to not work as expected. 
  • 88261: Attempting to download a PDF file may fail if the PDF template contains an image that is hosted on a site using "HTTPS" in the URL. As a workaround, use an image that does not contain "HTTPS" in the URL. 
  • 87908: For instances that use SugarIdentity, the Reset Multi-Factor Auth option improperly appears during a user impersonation session.
  • 87701: Naming a custom field "processed" causes web logic hooks to fail to fire because it conflicts with Sugar's internal logic hook handling. As a workaround, use a different, un-reserved string as the field name.
  • 87602: In Sugar Enterprise, portal customization settings for the following features in Admin > Sugar Portal > Theme Portal are available but not applicable to the portal: the search bar, the banner, and the dashboard.
  • 87601: In Sugar Sell, portal customization settings for the following features in Admin > Sugar Portal > Theme Portal are available but not applicable to the portal: the search bar, the banner, the New Case button, and the dashboard.
  • 86285: In certain circumstances, users may experience unexpected behaviors when attempting to expland a subpanel or edit an empty Subpanel layout in Admin > Studio. For information on the workaround, refer to the issue's description in the case portal. 
  • 85589: Saving the SAML settings may fail with an error "Maximum Length should be positive value" when the maximum length is not set for Sugar password requirements. 
  • 85246: Errors may get logged in the system after upgrading or installing Sugar when certain license data is missing.   
  • 84426: The Meeting Type field in the Meetings module does not reflect new values added to the Meeting Type dropdown list in Admin > Dropdown Editor.
  • 83796: SugarBPM processes always run after module-level logic hooks and it is not possible to configure them to run before logic hooks.
  • 83425: Custom Date fields in the PDF template may not respect the user's preferred date format. 
  • 82810: Fields based on non-existent or improperly defined custom field types may cause upgrades to fail.
  • 82742: The Forecast Bar Chart Dashlet may not load as expected in shared dashboards.
  • 82361: Emails sent from SugarBPM's processes may not include the link to new lead records generated from a Web-to-Lead form even though the process email template contains a link variable.
  • 81722: Sorting the fields by the column header (e.g., Name) in Admin > Studio or Module Builder may result in CSRF errors being written to the log file.
  • 81382: Deleting a target list related to a large number of records may fail with an error. 
  • 81297: If a web-to-lead form gets submitted using an existing email address in Sugar, the email address may not be marked as "Primary" for the generated lead record. 
  • 80865: It is not possible to search by the Record Name column in Process Management.
  • 80001: Email messages sent via SugarBPM may display HTML formatting when records are created using SOAP/REST v4.1. It is recommended to use the latest version of the API.
  • 79009: When the targeted module contains a broken field, configuring an Action element in a process definition causes the Process Design canvas to time out.
  • 77719: If a process definition contains a Wait event that is relative to a date field, the process does not adjust for changes that may occur to the date field after the Wait event's initiation.
  • 77287: Performing certain actions (e.g., import, mass update) in Sugar may result in performance issues if there are numerous calculated fields to be updated in related records. As a workaround, add the following line to the config_override.php file to disable the related calculation field updates: $sugar_config['disable_related_calc_fields'] = true;. But keep in mind that the affected calculated values will not be updated and running Recalculate Values on related records. 
  • 77249: Guests may not get imported to call or meeting records as expected.
  • 77055: Attempting to mass update the user's outbound email client via Admin > User Management may not work as expected.
  • 73566: Calculated or dependent fields containing a related() function may not get calculated until after save for activity-type modules (e.g., Notes).  
  • 68112: Matrix-type reports display incorrectly when exported to PDF.

Supported Platforms

For information on supported platform components, see Sugar 13.0.x Supported Platforms.

Upgrade Paths

Sugar Enterprise Upgrade Paths
Package From Version(s) MySQL SQLServer DB2 Oracle
New Installs
12.0.3-to-13.0.1 12.0.3 ✓ 
13.0.0-to-13.0.1 13.0.0