Let the platform do the work
SugarClubContact+1 (877) 842-7276

Sugar Enterprise 26.1.0 Release Notes

Overview

This document describes the changes and functionality available in Sugar Enterprise, Sugar Connect, Sugar Connector for LinkedIn Sales Navigator, Sugar Market, and SugarIdentity.

For more information and supporting materials related to this release and other SugarAI products, please review the May 2026 page in Release Central in SugarClub.

Sugar Enterprise

This section describes the changes and functionality available in Sugar Enterprise 26.1. While version 26.1 is available for both SugarCloud and on-site deployments, Sugar Enterprise is supported as an on-site deployment only.

For information about any changes to existing functionality in this release, you can also refer to the What to Expect When Upgrading to 26.1 article.

Feature Enhancements When Upgrading From 25.1

Features Common to All Enterprise Editions

The following feature enhancements are new in Sugar Enterprise On-Site 26.1 when upgrading from the 25.1 release:

Administration
  • Improved dropdown management: Managing dropdown lists is now faster, more flexible, and more user-friendly with several key enhancements.
    • Streamlined user experience: Sugar’s updated interface offers a cleaner, more intuitive view when creating and modifying your dropdown lists.
    • Enhanced search functionality: Quickly locate and update dropdown entries with the new built-in search capability.
    • Restore to Default option: Easily revert dropdown lists to their original state with a convenient “Restore to Default” feature.
    • Inline editing: Make quick adjustments to individual dropdown values directly within the editor.
  • Dropdown list formatting: You can now add styles to dropdowns to make information stand out at a glance.
    • Text styling: Apply predefined styles or use custom styling (e.g., bold) and colors.
    • Icons: Choose from a library of icons to display next to dropdown values.
    • Preview: Instantly preview your formatting before saving.
    • Consistency: See styles applied consistently across Sugar, including list views, record views, and reports.
    • Pre-styled dropdowns: Benefit from the feature immediately with predefined styles already applied the Sales Stage, Quote Stage, Lead Status, and Case Status fields.
  • Improved currency configuration: A text field for setting a system default currency has been added to Admin > Locale. Users can also opt to use this currency system-wide from their user profile.
  • Scheduler run order: A new field "Run Order" has been added in the Schedulers module to configure the priority order in which schedulers execute when multiple are scheduled to run simultaneously.
  • Scheduler time zone improvements: The schedulers user interface clearly shows when the next scheduled job will run based on the administrator's local time zone and in UTC.
  • Name formatting: The "LastFirst" name format (e.g., SmithJohn) has been added to the default list of name formats in Admin > Locale for use in languages such as Chinese.
  • SugarLive upgraded: SugarLive has been upgraded for compatibility with version 2 of the Amazon Lex bot.
Dashlets
User Interface
  • Doc Merge and relationships: Doc Merge can now retrieve data from one-to-many and many-to-many relationship fields to populate values from these relationships in generated documents.
  • Meetings module fields: Three new text fields, "Recording URL," "Summary," and "Transcript", have been added to the Meetings module to store meeting details.
  • Accessibility improvements: Some improvements have been made to keyboard navigation and screen reader support in Sugar to enhance usability and better align with accessibility standards.
  • Audit log pagination: Pagination has been added to the audit log to improve performance and usability when viewing large sets of audit data.
  • TinyMCE editor upgraded: The TinyMCE editor used in certain modules (e.g., PDF Manager, Emails, Knowledge Base) has been upgraded to version 6.8.6, bringing user interface enhancements and fixed issues.

Fixed Issues When Upgrading From 25.1

Click a panel to expand and view the fixed issues that are new in Sugar Enterprise 26.1 when upgrading from 25.1.

User Interface
  • 99167: The Web Page dashlet failed to load content for URLs containing the sugarai.com domain. This issue has been resolved, and the Web Page dashlet now loads content from this domain as expected.
  • 99037: The Document Revisions list view failed to load properly when navigating to it in Sugar. This issue has been fixed, and the Document Revision list view now loads as expected.
  • 98412: Sorting a module’s list view by a currency field column resulted in database errors. Now, sorting the list view by currency field columns works as expected.
  • 98409: When dropdown list values were formatted using the "Enable formatting in dropdown" option, the changes did not appear in the UI unless the user performed a hard browser refresh. Now, the dropdown formatting changes appear in the UI without manually refreshing the browser.
  • 98342: In certain circumstances, accessing the activity stream view from a module's list view (e.g., Cases) resulted in a 500 error. This issue has been fixed, and users can now access the Activity Stream in the module's list view as expected.
  • 98159: When filtering a list view by “Assigned To” using the “contains” operator, customers with large record volumes could experience performance issues or encounter an unknown error. To address this, the “contains” operator for the “Assigned To” filter has been changed to “is”.
  • 98128: Sugar displays a generic Database Failure message when a module contains a large amount of data that takes too long to load due to query timeouts. This has been fixed, and a more meaningful error message now displays in the UI.
  • 98097: Global search did not work as expected for certain users. Now, global search works as expected.
  • 97985: Required fields that were hidden in list view or subpanel columns were not validated when saving inline edits. Validation is now enforced for hidden required fields.
  • 97929: The Cases list view failed to load with an error message when there was a visibility dependency for related accounts or contacts. This has been fixed, and the Cases list view now loads successfully.
  • 97916: The Cloud Drive dashlet only displayed the first twenty folders for SharePoint, and attempting to access a folder that is not in the first twenty resulted in an error. Now, all folders in SharePoint can be accessed in the dashlet.
  • 97564: Clicking on a field while inline editing in a module's list view caused the page to scroll horizontally unexpectedly. Now, the page no longer scrolls unexpectedly when clicking on a field to inline edit.
  • 97533: An invalid filter called “Target Accounts” improperly appeared in the Accounts module. We have removed the invalid Target Accounts filter from the system so that it no longer appears in the Accounts module.
  • 97481: Global search failed to return results for records with comment log entries exceeding 32,766 bytes. Global search now successfully returns records with large comment logs.
  • 97372: When regular users attempted to access the Currencies module, the list view failed to load with a 403 error. Users are now allowed to access the module in read-only mode and view the list of available currencies in Sugar.
  • 97271: The "Related to current record" option was missing from the list view dashlet when adding it to the Home page. The "Related to current record" option now appears as expected when adding the list view dashlet on the Home page.
  • 97248: When a user assigned to a custom role where access to a module (e.g., Accounts) was disabled, re-enabling the module did not make it appear in the user’s account as expected. Now, re-enabled modules appear in the user’s account as expected.
  • 97216: The Show More link displayed an incorrect label (e.g., Show More Cases) for text area fields (e.g., case description). The label now correctly displays as "Show More".
  • 97006: When using OpenSearch, the global search failed to return search results if more than three search terms were entered in the search box. Now, entering more than three search terms returns matching records as expected.
  • 96989: The Username field was unavailable as a list view filter item for the Users module in Admin > Studio for versions 14.0 and higher. We have addressed this, so that the Username field is available as a filter option for the Users module.
  • 96982: If the Documents module contained document records with blank names, users encountered an error in the Documents list view and subpanel where the records failed to load. We have addressed this issue so that affected instances no longer encounter this error.
  • 96974: After the Related To field has been set for the record (e.g., calls, meetings), users can no longer edit the field as it becomes disabled. We have addressed this to allow users to update the Related To field in records.
  • 96899, 96484, 93648: In certain circumstances, the Timeline dashlet failed to load with a persistent Loading message. The Timeline dashlet now loads as expected.
  • 96280: Navigating the record view fields using the keyboard did not work as expected. Using the keyboard to navigate record view fields now works as expected.
  • 96208: In certain circumstances, funnel charts in Report dashlets were scaled incorrectly and got cut off when resizing the browser window. Now, funnel charts display properly when resizing the browser window.
  • 96186: The Downloads tab remained visible in the user’s profile even though the Display Downloads Tab option was disabled in Admin > System Settings. We have fixed this so that the Downloads tab is hidden when the Display Downloads Tab option is disabled in Sugar.
  • 96183: When a duplicate record was detected in Sugar, the duplicate check list that appeared displayed blank cells and columns in the layout. Blank cells and columns no longer appear in the duplicate check layout.
  • 96140: When converting a lead record that has the same name as an existing contact, certain options (e.g., Ignore and create new) on the Convert Lead page did not appear or work as expected. Now, the "Ignore and create new" option displays as expected when converting leads.
  • 96073: The Edit button for certain modules' record views (e.g., Accounts) may be shifted if the order of the Follow element has been altered in the record view layout's panel_header definition. The Edit button no longer shifts when changes are made to the record view layout.
  • 96021: When Hint retrieved multiple companies matching the name entered in the accounts Name field, selecting the desired company did not work as expected and the incorrect company was chosen instead. Now, users can select the correct company to populate the account data in Sugar.
  • 95979: Repeat-type fields in Meetings did not respect the field-level permissions set for a role. The field-level permissions set for Repeat-type fields are now respected properly in Sugar.
  • 95108: The audit log in the Cases module failed to capture the full text in the audited Description field if it exceeded 255 characters. The Description field now captures the full text as expected.
  • 95058: The list view's activity stream did not display a scrollbar, preventing users from scrolling to view the additional posts in the activity stream. The scrollbar now appears and users can scroll through all posts in the list view's activity stream.
  • 94987: The Claim, Unassign, and Close action buttons did not validate required fields, allowing the action to proceed even though the mandatory fields were incomplete. Now, required fields are validated as expected, and the actions will not execute until the requirements have been met.
  • 94690: When the administrator enabled team-based permissions, the Selected checkbox option did not appear in the users' Default Teams field as expected. Now, the Additional Permissions option is available to select for the users’ Teams field.
  • 93677: In certain circumstances, adding a note to a module record via the Notes subpanel would incorrectly trigger an unsaved changes warning when navigating away from the record, even though the note had been saved. This warning is no longer incorrectly triggered when adding notes to a module record.
  • 92769: The Record View dashlet failed to load in the focus drawer when a module record (e.g., accounts) used the "Required If" formula containing a related link reference. The Record View dashlet now loads as expected in the focus drawer.
  • 92739: The currency name (e.g., US Dollars) displayed in the user's profile was incorrect and did not match the updated default system currency (e.g., Euro) in Admin > Locale. The user's profile now displays the currency name as "System Currency (Default)" instead to denote the system's default currency.
  • 92217: On Windows or Chrome browsers, the texts in the Product Catalog dashlet appeared blurry or distorted making it hard to read. This issue has been fixed, and the text now displays properly in the Product Catalog dashlet.
  • 92089: In certain circumstances, the actions dropdown in the module's list view disappeared when a field used the Read Only If formula with the related() function. This issue has been fixed, and the actions dropdown now remains visible in the list view.
  • 92022: The "Required if" formula in a module (e.g., Cases) failed to enforce field requirements when it referenced values on the assigned user's record, due to permission issues. This issue has been fixed, and the "Required if" formulas now enforce field requirements as expected.
  • 90153: In certain circumstances, sorting the Documents subpanel by Name field caused unexpected server issues. Sorting the Documents subpanel by Name field now works as expected.
  • 89984: When a field that was previously marked as read-only in Sugar was updated to be editable, the change was not respected properly and the field continued to behave as read-only. This issue has been fixed, and the updated field now becomes editable as expected.
  • 89679: Removing a relationship in a module (e.g., Accounts) caused an error when loading another record (e.g., contacts) in Sugar. This issue has been fixed, and contact records now load properly when relationships are removed.
  • 89481: In certain circumstances, the Timeline dashlet appeared blank and failed to load in certain modules. We have fixed this issue, and the Timeline dashlet now loads as expected.
  • 89163: When filtering the Knowledge Base module using the Body field, the input field did not appear as expected when selecting the "containing these words" or "excluding these words" operators. The input field for these operators now display properly, allowing users to enter values to filter the Knowledge Base module using the Body field.
  • 88535: Dropdown fields in Advanced search for legacy modules defaulted to empty values and caused no search results to return. The dropdown fields in Advanced search no longer default to empty values.
  • 83020: List view counts were inflated when filtering by multiple tags using the "is any of" operator, because records matching more than one tag were counted multiple times. The list view count is now displayed correctly when filtering by multiple tags.
  • 82479: When the Knowledge Base module's Body field was modified in Studio, the system incorrectly applied a 255-character limit to the field. This has been fixed to no longer apply a limit to the Body field.
  • 80435: Users assigned a role with View permission set to "Owner" for a module (e.g., Accounts) could not be tagged in the activity stream for records (e.g., accounts) they owned the record. The affected users can now be tagged as expected in the activity stream for records they own.
  • 80275: Related() formulas using parent record fields did not display the data correctly in the related record subpanel. This has been fixed, and the value of the field now displays correctly in the subpanel as expected.
  • 73566: Activity records using custom flex relate calculated fields failed to populate values when a related record was added. This issue has been resolved, and these fields now populate as expected.
Administration
  • 98885: In certain circumstances, customer instances became unresponsive due to PHP fatal errors caused by stale cache entries. This issue has been fixed, and the errors no longer occur.
  • 98643: The dropdown lists in Admin > Dropdown Editor failed to load for users assigned a role with Admin & Developer access. Now, users with Admin & Developer access can access and edit the dropdown lists as expected.
  • 98602: There was no validation check performed when adding dropdown list item names in the dropdown editor. Now, a validation check has been added to the dropdown editor to ensure that only valid item names are added.
  • 98411: In certain circumstances, making changes in Admin > Studio resulted in unexpected performance issues in the system. This has been fixed, and making changes in Studio no longer cause instances to become unresponsive.
  • 98237: The sales stage and dropdown colors were lost after installing or uninstalling a module in Sugar. This has been fixed, and installing/uninstalling a module no longer causes the sales stage and dropdown colors to be lost.
  • 98233: Clicking the SugarCloud Insights link on the Administration page failed to open in Sugar 25.2. Now, the SugarCloud Insights page opens as expected when clicking on the link.
  • 98095: In certain circumstances, some SugarCRM log files appeared empty. This has been fixed, and the log files appear correctly.
  • 98094: When a smart guide activity was configured to trigger a Sugar action that has the user create a pre-populated record, the fields were not being pre-populated. Now, the fields are pre-populated as expected.
  • 98068: Updating a private team name (e.g., John Smith) with more than two words caused the user's last name to be appended incorrectly. Now, the user's last name does not get appended to the updated private team name.
  • 97835: Module loadable packages that referenced a piece of code in a previous package failed to install due to a PHP error. The module loadable packages affected by this issue can now be installed successfully.
  • 97467: The Filter API response did not return fields in the order defined in the field's parameter when fields were added or modified in a module. The Filter API response now returns fields in the correct order defined in the field's parameter.
  • 97450: Process definitions intended to create a record related to the target module's related record (i.e., a two-away relationship) were creating an invalid record in the one-away module instead when triggered via import to the target module. This has been fixed so that the two-away record is created as expected.
  • 97335: For instances with a Sugar Market license, users assigned to a Sugar Enterprise license were not automatically assigned to the Market license after upgrading to version 25.1.0. We have addressed this to ensure that users meeting the criteria are automatically assigned to the Market license during upgrade.
  • 97179: In certain circumstances, the Configure API Platforms page in Sugar displayed an empty API platforms list for administrators not assigned to a Sugar Market license. We have addressed this to ensure that the Configure API Platforms page displays the list of platform identifiers as expected for administrators.
  • 97131: Calls to the filter API returned unexpected results after upgrading to Sugar 25.1.0. We have addressed this so that affected instances no longer encounter this issue.
  • 97112: When administrators previewed the layout configuration for Actions Buttons in Studio, the Edit button and Actions menu were misaligned resulting in styling issues. We have addressed this to ensure that the button and menu align and display properly in the preview.
  • 97111: In certain circumstances, installing Sugar 25.1.0 failed to complete and resulted in an error. This has been fixed, and the installation now completes successfully.
  • 96935: Conditional required fields were not properly enforced in Sugar Automate tasks, allowing records to be saved when required fields were blank. Now, a validation error is triggered as expected when the required field is blank.
  • 96912: In certain circumstances, a PHP error occurred during a health check for upgrades or when exporting customizations in Sugar. We have addressed this issue so that affected instances no longer encounter this error.
  • 96626: When a Smart Guide was cancelled via a SugarBPM process, it initially timed out with an error. Now, users no longer see a time out issue when a Smart Guide gets cancelled via a SugarBPM process.
  • 96552: Modifying an out-of-the-box dropdown in Studio caused exported module customizations using that dropdown to fail installation during the package scanning step. Now, the installation completes successfully as expected.
  • 96537: The Update Momentum of In-Progress Smart Guides scheduler failed with an error when the Momentum Score or Momentum Points fields contained NULL values. Now, the Update Momentum of In-Progress Smart Guides scheduler runs as expected.
  • 96487: Calculated fields using the maxRelatedDate() function were not automatically recalculated if the related module was created via the subpanel or quick create. Now, the calculated fields are automatically recalculated as expected.
  • 96261: Attempting to update an integer field with a blank value failed and resulted in an error. This has been fixed, and the integer field can now be set to a blank value.
  • 96260: Certain settings (e.g., dashboards, filters) and buttons (e.g., Confirm, Apply) on the page layout were missing from the Copy Preferences and Content page in User Management. The settings and buttons now appear on the page as expected.
  • 96157: When a record was linked via a subpanel (e.g., Teams) in the user's profile, the user's preferences under the Advanced tab were unexpectedly cleared. This has been fixed, and the user settings no longer get cleared in the Advanced tab.
  • 96102: Certain changes made in before_save logic hooks were not recorded in the audit log as expected. The changes are now logged as expected in the audit log.
  • 96057: In certain circumstances, the quick repair and rebuild process failed to rebuild the cached PHP files causing instances to become unresponsive and generate errors in the user interface. This has been addressed, and the quick repair and rebuild runs more smoothly.
  • 95652: In certain circumstances, Sugar retained more log files than the configured maximum in the system due to differences in date formats across log file names. This issue has been fixed, and older log files are now properly cleaned up to enforce the configured limit.
  • 95495: The SugarBPM process validator failed with a 500 error if the process definition used the Change Field action. This issue has been fixed, and the system successfully validates the SugarBPM process when the Change Field action is used.
  • 95478: Performing a manual license validation offline in Sugar improperly caused the Sugar Automate license and features to disappear from Sugar. We have addressed this, and the Sugar Automate features remain as expected after manual license validation.
  • 95384: The Filter API returned incorrect offsets and record counts, and some records were missing in JSON results when modules included multiple related links in the query. The API now returns the correct record counts.
  • 95297: Creating a new user in Sugar with the same username as an existing user generated an incorrect error message pertaining to a different issue. Now, the correct error message appears indicating what the issue is and the appropriate next steps.
  • 95226: Time elapsed legacy workflows that were set to execute before a specified time did not work as expected and were triggered incorrectly after the date had passed. Now, workflows that are set to trigger before a specified time work as expected.
  • 95066: Attempting to delete a group user in SugarIdentity-enabled instances failed with an error. Now, group users can be deleted for SugarIdentity-enabled instances.
  • 94464: Users experienced unexpected behaviors with the Reassign Records function in the Users module. We have addressed this so that affected users no longer encounter this issue.
  • 94268: In certain circumstances, creating new records (e.g., case) with attachments failed to save with an error when a related SugarBPM process attempted to update the parent record. This issue has been fixed, and records with attachments now create successfully without errors.
  • 94079: Searching for inactive users in the Users module's list view did not return inactive users in the search results as expected. Now, the search result returns inactive users as expected.
  • 94065: Copying filters to all users on a team (e.g., East team) using the Users > Copy Contents option did not assign the filter to all team members as expected. All members of the selected team are now assigned the copied filter.
  • 93985: The PMSE “First Update” logic triggered again on subsequent record updates after the Data Archiver hard deleted or archived records in the pmse_Inbox module. This issue has been fixed and the process does not trigger again.
  • 92083: Audited Deleted module fields did not track changes as expected. This issue has been fixed, and they now track changes correctly.
  • 91975: The Process Business Rules Builder failed to load when certain target modules (e.g., Leads, Opportunities) were disabled for Sugar Automate. This issue has been fixed and the Process Business Rules Builder now loads as expected.
  • 91898: A database error occurred for instances with a large number of calculated fields with relate function. We have fixed this issue, and the affected instances no longer encounter this error.
  • 89542: When instances contained a very large number of SugarBPM processes, the Process Management's list view failed to load or experienced performance issues. This issue has been fixed, and the Process Management list view now loads as expected.
  • 89352: For instances using dark mode in Sugar, the parent dropdown option labels in the visibility editor window in Admin > Studio were not readable. The parent dropdown labels are now readable in dark mode.
  • 89298: When a custom Logic Hook resulted in an error during the execution of a Process Definition (e.g., updating related Cases from an Account save), the error was suppressed during Security Context deactivation, causing a generic error message to appear in the UI. This has been fixed, and users now see a meaningful error message in the UI when this issue occurs in the system.
  • 86963: Users were unable to change a Relate type field using the Change Field action in a SugarBPM process definition. This issue has been fixed, and users can now change the Relate type field using the Change Field action in SugarBPM.
  • 86770: When records (e.g., accounts) were deleted in Sugar, the Prune Database on 1st of Month scheduler did not delete the related audit records as expected. The Prune Database on 1st of Month scheduler now deletes the audit records related to the deleted parent record.
  • 86285: In certain circumstances, admins were not able to add fields to a subpanel layout in Admin > Studio. We have addressed this issue, and fields can now be added to subpanel layouts as expected.
  • 85246: Unexpected errors were logged in the system after upgrading or installing an instance when certain license data was missing. We have addressed this issue, and the affected instances no longer encounter this issue.
  • 84205: The deleted user's private team was incorrectly available for selection in the Teams field in Sugar. This issue has been addressed, and the deleted user's private team is no longer available to select.
  • 82950: When a custom Sugar Logic expression package was uninstalled, any calculated fields referencing the removed function caused an unhandled exception during metadata cache rebuild, resulting in the instance becoming inaccessible with 500 errors. We have addressed this issue, and the affected instances no longer encounter this issue.
  • 82401: In certain scenarios, records that had completed a BPM process could not trigger the same process again. This has been fixed so completed processes are properly finalized, allowing records to re-trigger processes as expected.
  • 81905: Invalid formulas were incorrectly allowed to be saved in Studio which caused the instance to become inaccessible due to server errors. Now, an error message appears when invalid formulas are detected to prevent this issue.
  • 81722: Sorting the module's (e.g., Accounts) fields table in Admin > Studio resulted in fatal errors in the system. This issue has been resolved, and sorting the fields in Studio no longer generates an error.
  • 81551: Email template fields are not localized based on the recipient’s language and date-time preferences when sent via the BPM "Send Message" object. This issue has been address and now values and date fields use the recipient’s language and date-time preferences.
  • 80852: The Prune Database scheduler job failed to prune all database tables due to timeouts when one or more tables were too large or heavily used. This has been fixed, and the Prune Database scheduler job no longer stalls on large tables.
  • 80415: Adding new dropdown options to dropdown lists while switching languages caused the dropdown list to not remain in sync across languages resulting in inconsistent dropdown values. Modified dropdown lists made in one language are now reflected correctly across all languages.
  • 78326: Deleted user records incorrectly appeared in the user's list when reassigning records in the Users module. This issues has been fixed, and deleted user records are no longer available to select when reassigning records.
  • 77719: If a process definition contained a Wait event that was relative to a date field, the process did not adjust for changes that may have occurred to the date field after the Wait event's initiation. We have fixed this issue, and Wait events now update correctly to ensure that the process gets triggered as expected.
  • 77548: Editing the calculated formula for Currency-type fields (e.g., Total Amount) in Studio resulted in errors when the formula contained the isNumeric function. This issue has been fixed, and currency fields using the isNumeric function now saves as expected in Studio.
  • 77365: Default values for custom fields that exceeded 255 characters were truncated even through the field's Max Size was set to a higher value (e.g., 400), due to a limitation in how default values were stored. This issue has been fixed, and default values now respect the field's Max Size value and no longer get truncated.
  • 77287: Users were not informed that performing large imports containing calculated fields from related records could impact performance. Users now see an informative message in the import wizard indicating that these large imports may take several minutes to complete.
  • 77087: Switching the user's default team from their private team to another team (e.g., Global) incorrectly caused the user's last name to be appended to the newly selected team's name (e.g., Global Smith). This issue has been fixed, and the user's last name no longer gets appended to the newly selected team's name.
  • 75712: Changing the order of the dropdown items in the parent_type_display dropdown list did not get preserved as expected. Now, dropdown items are displayed in the correct order after save in the dropdown list.
Reports and Forecasts
  • 98488: When the Forecasts fiscal year start date was set to a date other than January 1st, drilling through the opportunities report chart did not display the correct records matching the criteria. Now, the correct records display as expected when drilling through the opportunities report chart.
  • 98259: When attempting to schedule a report from the Advanced Reports list view, the pop-up window to schedule the report did not open as expected. This has been fixed, and the pop-up window now opens to allow the user to schedule the report.
  • 97947: The US Dollar fields (e.g., List Price (US Dollar), Book Value (US Dollar)) in reports were incorrectly displayed using the record’s currency instead of US dollars. Now, the US Dollar fields are correctly converted to US dollars in reports as expected.
  • 97538, 97476: Currency fields in reports incorrectly displayed the system currency or the user’s preferred currency instead of the record’s selected currency. Now, the currency fields properly respected the record’s selected currency.
  • 97269, 97262, 97261: Users experienced performance issues when accessing certain summation reports or managing their Report dashlets in Sugar due to redundant operations in the system. Now, users are able to access the summation reports and Reports dashlets as expected.
  • 97252: Users experienced unexpected performance issues when previewing reports displaying SQL queries. We have addressed this so that users can view the reports without running into unexpected issues.
  • 97243: In certain circumstances, the report charts did not respect the user’s preferred currency (e.g, €) and displayed an incorrect currency symbol (e.g., $) instead. We have addressed this to ensure that the report chart displays the user’s preferred currency as expected.
  • 97195: Dates displayed incorrectly in reports for users using the UK date format (e.g., DD-MM-YYYY). Dates in reports now display correctly for users using the UK date format.
  • 96698: When the Forecast fiscal year start date was set to a date other than January 1st, drilling through the opportunities report chart did not display the correct records matching the criteria. Now, the correct records display as expected when drilling through the opportunities report chart.
  • 96426: Sorting report results by a field column (e.g., Likely) did not work as expected if the column contained multiple currencies (e.g., $, €) for the records. This has been fixed, and the field column in the report now sorts as expected.
  • 96346: When reports were grouped by DateTime fields (e.g., Day: Start), the users' time zone was not respected properly, resulting in incorrect report results. This has been fixed, and the report results are generated correctly.
  • 95763: Attempting to view reports containing a deleted field failed to generate and resulted in a database error. Now, a meaningful error message appears in the UI informing users of the next steps to take to remove reference to the deleted field.
  • 95685: When a report failed to generate due to a large data request, the error message incorrectly stated it was a permission error. Now, the correct error messaging appears and informs users of the next steps to take to resolve the issue.
  • 95294: Chart (e.g., funnel) elements in reports were incorrectly displayed in a single color. This issue has been fixed, and the report chart elements now display using the appropriate colors.
  • 94709: Invalid dates in report filters were only detected when the report was run and not during the report creation. Now, users are alerted of invalid date formats during report creation.
  • 94233: When a Report dashlet was added to a module's record view (e.g., Accounts) with the Related to Current Record option enabled, the dashlet did not filter based on the current record (e.g., ABC Company). This issue has been fixed, and enabling the option now correctly displays the report result filtered by the current record.
  • 93489: Report filters comparing DateTime fields to static values did not respect the user's time zone or the DST adjustments causing incorrect report results. This issue has been fixed, and the report results now correctly display the time zone and DST adjustments.
  • 93178: Exported reports returned an error for users assigned a role with Export permission set to "Owner" for the particular module (e.g., Meetings). The affected users can now export reports successfully.
  • 92978: Document names were not linked properly in reports and could not be clicked to open the record in Sugar. We have addressed this to ensure that document names are linked and can be clicked to access the document record.
  • 92055: Numbers in report charts sometimes displayed in white making it hard to read for certain bar colors. The text color in charts is now determined by the bar's background color to ensure consistency and readability.
  • 91803: When users were restricted from accessing certain reports, they received a generic error message that was not clear. Users now see a meaningful error message indicating the access issue.
  • 89991: Reports created using denormalized records previously failed to open after normalization was disabled for that record type; this issue has been resolved, and affected reports no longer encounter this behavior.
  • 87080: Summation With Details reports grouped by dropdown lists (e.g., Sales Stage) displayed data incorrectly when the dropdown options were deleted or renamed. This issue has been resolved, and the data in the Summation With Details report now displays correctly in the generated/exported report.
  • 86985: Invalid queries entered in the Advanced Reports Custom Query builder generated a 404 error instead of a meaningful error message. Users now see an informative message indicating that the query is invalid.
  • 80778: Report charts in Matrix or Summation With Details reports were not sorted according to the sorting defined in the report's settings. The report charts are now sorted correctly as defined in the report's configuration.
  • 79984: When creating a report (e.g., Summation With Details report), the Sum/Min/Max/Avg Duration Minutes fields were not available to select in the Choose Display Summaries step. This issue has been fixed, and the Duration Minutes options now appear as expected when setting the display summaries in the report.
  • 77564: When advanced reports were exported, the export delimiter (e.g., ",") in the CSV file did not match the user's preferred setting (e.g., ";"). The exported CSV file for advanced reports now shows the correct export delimiter.
  • 75263: For reports that were scheduled before daylight savings time occurred, the time did not get adjusted properly for subsequent scheduled runs, causing a 2 hour discrepancy. Users are now alerted when the scheduled report times do not align with the current system time vs the user time.
Email and Calendar
  • 98525, 98344: Sorting by certain field columns (e.g., Date Sent) in the Emails subpanel of the Cases module resulted in a database error. This has been fixed, and sorting by a field column in the Emails subpanel now works as expected.
  • 98387: When using the Reply All feature in an email, the email addresses matching the outbound email addresses in the From, To, CC, and BCC fields were removed in the new reply message. This issue has been fixed, and the email addresses in the From, To, CC, and BCC fields are copied to the new reply message.
  • 98367: Users with email accounts configured via Exchange Online were prevented from sending mail using other approved email addresses. Now, users can send mail using other approved email addresses.
  • 98254: Sugar failed to send multiple campaign emails when the system’s outbound email setting was configured for Exchange Online. Now, multiple campaign emails are sent without errors in Sugar.
  • 98123: In certain circumstances, paginating through the Emails subpanel in case records timed out for instances with large volumes of email data. This issue has been fixed, and pagination now works as expected.
  • 98065: Users were required to re-authenticate their Microsoft account every 90 days even though the account was used regularly. This has been fixed, and users no longer have to re-authenticate their Microsoft account.
  • 97804: When any emails failed to import to Sugar due to a system error, the inbound email scheduler stopped running causing subsequent emails from being imported. We have addressed this to prevent the scheduler from stalling so that emails get processed and imported as expected.
  • 97607: A 500 error occurred in the Emails subpanel and Timeline dashlet when loading archived emails indirectly related to contacts with a large number of emails. We have addressed this so that affected instances no longer encounter this issue.
  • 97600: When two contacts records were merged, the primary record's email address was blank even though it existed in the record. This has been fixed, and the primary record's email address appears as expected now.
  • 97439: Changing the related module (e.g., from a contact to an account) for a held call or meeting failed to save with a PHP error. Users can now change the module related for held calls and meetings.
  • 97355: When the same Sugar instance was open in multiple browser tabs, changes made to Calendar settings in one tab improperly overwrote the settings in another tab. This issue has been fixed, and Calendar settings now remain consistent across tabs.
  • 97302: Email addresses were improperly omitted from archived emails in Sugar if the display name contained an apostrophe (e.g., A’drian Smith). Now, apostrophes are no longer misinterpreted as a malformed quote, and these email addresses can be included in the archived email.
  • 96663: In certain circumstances, long email texts were improperly cut off when viewed in a module's record view (e.g., Emails, Cases). Now, long email messages can be viewed properly using the horizontal scrollbar.
  • 96033: When logged in to Sugar using a non-English language (e.g., Chinese), setting the user's preferred time format to "23:00" caused unexpected issues when changing the start date and time for a meeting. This issue has been fixed, and and changing the meeting's start date and time no longer results in an error.
  • 95960: Emails imported to Sugar with invalid UTF-8 encodings caused unexpected issues, displaying blank content in the email record. Now, invalid UTF-8 characters are ignored and the email content is displayed correctly.
  • 95509: In certain circumstances, the inbound email scheduler failed to archive all emails and users experienced premature removal of emails from their inboxes. Now, emails are archived properly and remain in the user's inbox as expected.
  • 95337: In certain circumstances, users encountered unexpected issues when logging in to SugarIdentity-enabled instances due to expired access or refresh tokens. Users can now log in without encountering unexpected issues.
  • 95333: The default refresh token lifetime setting was not respected for SugarIdentity-enabled instances and expired after 24 hours causing user sessions to timeout. Now, the refresh token lifetime no longer expires after 24 hours, and the user's session remains active.
  • 94980: The fields on the Forgot Password form were not visible for instances that were not SugarIdentity-enabled. This issue has been fixed, and the fields now appear as expected on the form.
  • 93750: When composing an email, removing the uploaded image from the user's email signature improperly removed the image from their default email signature. Removing the image from the email signature no longer affects the user's default email signature.
  • 92799: Fixed an issue where test emails could take longer than expected when certain email timeout settings were configured. Test emails now send within the expected timeframe.
  • 91932, 89408: Meetings without an assigned user appeared blank in the Calendar module and caused unexpected issues when attempting to open the record. Now, unassigned meeting events display as expected in the calendar.
  • 91283: After changing the primary email address, messages linked to the contact did not appear in the Emails list view when filtering by the primary email address. Now, filtering by the primary email address returns all related messages as expected.
  • 89500: Inline images were missing in emails replied to from Sugar. The inline images now display as expected in the replied-to email.
  • 89482: For instances using SAML, certain SAML users who were configured to authenticate through an external identity provider did not appear in the shared calendar list in Sugar as expected. The affected SAML users now appear in the shared calendar list as expected.
  • 87501: Inactive users were allowed to be added as guests when creating meetings or calls. This issue has been resolved, and inactive users can no longer be added as guests to meetings and calls.
  • 86774: In certain circumstances, setting the user's non-primary email address as the Reply-to address did not save the configuration changes in the user's profile. This issue has been fixed, and setting the user's non-primary email address as the Reply-to address now saves as expected.
  • 81859: When parent records (e.g., cases) of emails were merged in Sugar, the emails related to the deleted record were not automatically related to the resulting merged record. Now, the emails related to the deleted parent record are related correctly to the merged record.
  • 67377: In certain circumstances, the Check Inbound Mailboxes scheduler displayed error messages when downloading emails with attachments. Downloading emails with attachments no longer logs error messages in the scheduler.
Documents and Doc Merge
  • 98492: When a PDF template was edited and saved, previewing the template generated a blank PDF. We have fixed this issue, and the PDF template now generates the preview as expected.
  • 97329: Regular users encountered a permissions error when merging records (e.g., quotes) with a Doc Merge template containing a currency field. Users are now allowed to merge records with templates containing currency fields.
  • 97196: Performing a doc merge in a custom module failed to upload the files to the Cloud Drive dashlet. We have addressed this to ensure doc merge successfully uploads the files to the Cloud Drive dashlet.
  • 96302: Documents created via Doc Merge cannot be deleted from the system after they have been emailed as an attachment. Doc Merge documents can now be deleted from the system.
  • 96056: In certain circumstances, generating a document via Doc Merge failed to complete when a quick repair and rebuild was performed in Sugar. The Doc Merge completes successfully now.
  • 95819: When logged in to Sugar using a non-English language (e.g., Deutsch), the date format (e.g., MMMM-YYYY) in Doc Merge templates incorrectly displayed the month name in English instead of the user's preferred language. Now, the Doc Merge template respects the user's preferred language and displays the date correctly.
  • 95587: The order of comments and quoted line items in a quote document generated by Doc Merge did not match the order shown in the Sugar application. Now, the comments and quoted line items appear in the correct display order in the quote document.
  • 95285: When generating PDF files, the PDF incorrectly displayed the current date instead of the expected date (e.g., expiration date) when the user's default date format (e.g., MM-DD-YYYY) was not ISO compliant. Now, the PDF files display the dates correctly.
  • 95179: When a Document record was marked as "Is a template", users were unable to edit the document. Document records that are set as templates can now be edited as expected.
  • 94322: Users encountered unexpected issues when downloading PDF files that contained images with spaces in the file names. This issue has been fixed, and the PDF files now generate successfully.
  • 94295: PDF documents generated via Doc Merge failed to open when the document contained an ampersand symbol (&). PDF documents containing "&" now open as expected.
  • 93773: In certain circumstances, users experienced unexpected performance issues when performing a Doc Merge in Sugar. Users no longer experience performance issues when merging records.
  • 93519: Merging records containing TinyMCE fields via Doc Merge caused unexpected formatting issues in the merged document. TinyMCE fields now display correctly in the merged document.
  • 92836: In certain circumstances, the document merge failed to complete and remained in a processing state due to a metadata rebuild conflicting with the Doc Merge process. Now, the document merge process completes as expected.
Quotes
  • 97140: Users experienced unexpected issues when generating quotes via the Revenue Line Items record view or subpanel. We have addressed this so that users can properly generate quotes from revenue line items.
  • 94673: Editing a quote and its quoted line item at the same time caused the edited field values to not save correctly and display unexpected or incorrect values. The edited field values now save properly and display the correct values as expected.
  • 93684: When generating a quote from the Revenue Line Items submodule of an opportunity, the “Grand Total” initially appears as 0 until the quote is saved, regardless of the line item values. Draft quotes will now display the correct “Grand Total” before the record is saved.
  • 91455: Pasting email addresses in the quoted line item's Description field caused unexpected display issues. This issue has been fixed, and the text in the Description field now displays correctly.
  • 88374: Attempting to reorder the columns in the Worksheet Columns Preview list view in Admin > Quotes Configuration did not work as expected. Admin users are now able to reorder the columns in the Worksheet Columns Preview list view.
  • 82880: Fields (e.g., Description) that were marked as available in the Quoted Line Items module did not appear in the Quotes Configuration worksheet as expect
Opportunities, Revenue Line Items, Products
  • 98876: When adding a new revenue line item and then immediately modifying an existing revenue line item without reloading the page, the newly added revenue line item was not included in calculations for fields (e.g., Amount field). This has been fixed, and newly added revenue line items are now included in the calculation as expected.
  • 98647: In certain circumstances, the Show Changes functionality in the Opportunities module failed to load historical changes and resulted in fatal errors. This issue has been resolved, and the Show Changes functionality now works as expected.
  • 96358: An incorrect total amount was displayed in the Opportunities tile view when the opportunity records' currencies differed from the system currency or the user's preferred currency. This has been fixed so that the correct total amount now displays.
  • 95867: In certain circumstances, navigating the Product Catalog dashlet pages displayed duplicate records and caused “Show More” to become unresponsive. This issue has now been resolved.
  • 98580: The delta values were not displayed correctly for the Sales Stage field after changing the dropdown value labels in Studio > Opportunities. This issue has been fixed, and the delta values now display correctly for the Sales Stage field.
  • 98542: In certain circumstances, a PHP fatal error occurred in the Forecasts module due to issues with calculations. We have fixed this issue, and the affected instances no longer encounter this error.
  • 92792: Creating a revenue line item with a SugarBPM process definition triggered by Relationship Update resulted in a 500 error. This issue has been fixed, and revenue line items are now created successfully.
  • 88740: The Product Catalog record view failed to load when a relationship between the Product Catalog module and another module (e.g., Accounts) was deleted. This issue has been fixed, and the Product Catalog record view now loads successfully after the relationship gets deleted.
  • 76013: When creating an Opportunity, the Expected Close Date field in revenue line items did not auto-populate with a value as expected, even though a default value was set in Admin > Studio. This has been fixed, and the Expected Close Date field now gets auto-populated with a date as expected.

Developer

Please refer to the Developer Blog in the SugarClub community for a summary of the changes in version 26.1 that may affect developers.

Supported Platforms

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

Upgrade Paths

Sugar Enterprise Upgrade Paths

The following upgrade paths apply to Sugar Enterprise:

Package From Version(s) MySQL SQLServer DB2 Oracle
New Installs ✓ ✓ ✓ ✓
25.1.3-to-26.1.0 25.1.3 ✓ ✓ ✓ ✓

Sugar Connect

Click to expand the panel and learn about the Sugar Connect release.

This section describes the fixed issues available in this release of Sugar Connect. For more information about Sugar Connect, refer to the Sugar Connect documentation.

Fixed Issues

  • 98448: The German localization in Settings > Email Archival displayed the same label for both the outbound and inbound auto-archive options. This issue has been resolved and both options now display the correct German translations.
  • 98473: Under certain circumstances, users could continue to access Sugar Connect after their add-on license had expired. A license check has been added to the login process so that users are now properly logged out or blocked when their add-on license is no longer valid.
  • 98499: Users added via the Auto-Add functionality were not automatically linked to their CRM user records. This issue has been resolved and auto-added users are now linked as expected.
  • 98628: Images in Sugar email templates did not display when inserted into Outlook via Sugar Connect. This issue has been resolved and template images now render correctly.
  • 98848: In Gmail conversation view, the Sugar Connect Archive button was only functional on the most recent email in a thread. This issue has been resolved and the button now works on every message in a conversation.
  • 98977: Clicking a Scheduler confirmation link from Outlook could incorrectly show a "time no longer available" message. This issue has been resolved and confirmation links now work reliably across all email clients.

Sugar Connector for LinkedIn Sales Navigator

Click to expand the panel and learn about the Sugar Connector for LinkedIn Sales Navigator release.

This section describes the feature enhancements available in this release of the Sugar Connector for LinkedIn Sales Navigator. For more information about the Sugar Connector for LinkedIn Sales Navigator, refer to the LinkedIn Sales Navigator Connector documentation.

Feature Enhancements

  • Support for Sugar 26.x release: This version of the connector is supported for use with the Sugar 26.x release.

Sugar Market

Click to expand the panel and learn about the Sugar Market release.

This section describes the feature enhancements and fixed issues available in this release of Sugar Market. For more information about Sugar Market, refer to the Sugar Market documentation.

Feature Enhancements

  • Form improvements:
    • Required field highlighting: Required fields left incomplete after an attempted form submission are now highlighted in red, helping users quickly identify what needs to be completed.
    • Minor style enhancements: Spacing, borders, and cursor behavior for form elements have been enhanced.
    • Improved submission tracking: Market pages can now associate previously anonymous web activity with a contact when the visitor accepts cookies and submits a form. This applies only to Market pages, not external pages.

Fixed Issues

  • 99126: When creating an A/B test email with Email Content as the test factor, Email B would sometimes be removed after saving and returning to setup. This issue has been resolved, and both test emails now remain saved as expected.
  • 98984: For some customers, web activity captured for pages included in scoring profiles did not trigger lead score updates or appear in the Scoring Summary. This issue has been resolved, and qualifying web activity will now be scored correctly.
  • 98967: The preview and restore actions in Email Builder Revision History would sometimes produce an error. This issue has been resolved, and saved email revisions can now be previewed and restored as expected.
  • 98712: In some instances, web activity tracked on pages with form submissions was not associated with the corresponding Contact record, even though both the activity and form submission were recorded. This issue has been resolved, and web activity will now correctly associate with the related Contact.
  • 98322: Some tracked email link clicks that occur immediately after delivery were incorrectly recorded as human clicks. This issue has been resolved, and these bot clicks will now be correctly flagged.
  • 97887: Records were not sorted correctly when sorting by the Owner column in the Account Contacts list view within the Contact and Lead record views. This issue has been fixed, and records will now appear in the correct order.

SugarIdentity

Click to expand the panel and learn about the SugarIdentity release.

This section describes the fixed issues in this release of SugarIdentity. For more information about SugarIdentity, refer to the SugarIdentity documentation.

This release of SugarIdentity addresses minor product issues.