Sugar Serve 25.2.0 Release Notes

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

• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 97335: For instances with a Sugar Market license, users assigned to a Sugar Sell or 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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 user interface.
• 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.
• 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.
• 96899, 96484, 93648: In certain circumstances, the Timeline dashlet failed to load with a persistent Loading message. The Timeline dashlet now loads as expected.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 89500: Inline images were missing in emails replied to from Sugar. The inline images now display as expected in the replied-to email.
• 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.
• 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.
• 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.

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

• 98079: Customized role-based dropdown lists do not appear with an asterisk next to the role name.
• 97467: The Filter API response may not return fields in the correct order as defined in the field's parameter when a field gets added or modified in a module.
• 97439: Changing the related module (e.g., from a contact to an account) for a held call or meeting may fail to save with a PHP error.
• 97195: Dates may display incorrectly in reports for users using the UK date format (e.g., DD-MM-YYYY). As a workaround, use the YYYY-MM-DD date format instead to display the date values correctly.
• 96663: In certain circumstances, the email text may get cut off improperly when viewing the message in a module's record view (e.g., Emails, Cases). As a workaround, copy the text (e.g., CMD+A) and paste into a text editor to see the entire message.
• 96559: When using doc merge with quotes, the numbered line items for quotes may not display correctly in the merged document.
• 96407: In certain circumstances, a PHP error may occur when legacy workflows are triggered on Sugar instances running on PHP 8.3. For information on the workaround, refer to the issue's description in the case portal.
• 96346: When a report is grouped by DateTime fields (e.g., Day: Start), the users' time zone may not be respected properly resulting in incorrect data in the report result.
• 96260: The Copy Preferences and Content page in User Management may be missing certain settings (e.g., dashboards, filters) and buttons (e.g., Confirm, Apply) on the page layout.
• 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.
• 95983: In certain circumstances, the Update Momentum of In-Progress Smart Guides scheduler may fail with an error.
• 95495: In certain circumstances, the SugarBPM process validator may fail with a 500 error for older process definitions.
• 95337: Users may experience unexpected behaviors when logging in to SugarIdentity-enabled instances. For information on the workaround, refer to the issue's description in the case portal.
• 95333: The default refresh token lifetime setting may not be respected for SugarIdentity-enabled instances and expire within 24 hours causing user sessions to timeout.
• 95325: When using DocMerge to generate documents for records (e.g., quotes) with the same name, only one document record is created with multiple revisions linked to the different records instead of generating separate documents linked to each record. As a workaround, disable the Use Revisions option on the document template.
• 95294: The chart (e.g., funnel) elements in reports may incorrectly be displayed in a single color.
• 95176: The Doc Merge Region Configuration setting in Admin > System Settings may not show the correct region based on where the customer's instance is hosted.
• 94903: In certain circumstances, upgrading Sugar may fail with an error.
• 94709: When creating a report, entering an incorrectly formatted date in the date field causes the report generation to fail with an un-meaningful error message.
• 94322: Users may encounter unexpected issues when PDF files contain images with spaces in the file names. For information on the workaround, refer to the issue's description in the case portal.
• 94268: In certain circumstances, unexpected errors may occur when creating new records (e.g., cases, opportunities) in modules tied to a SugarBPM process.
• 94194: The data tables in reports may appear blank and show no data.
• 94192: Double clicking on a record's row in a custom module's list view does not open the inline editing mode as expected.
• 94079: Using the list view search in the Users module to locate inactive users does not return the users' records in the search results as expected.
• 93958: Matrix-type reports may improperly generate large amounts of messages in the sugarcrm.log file.
• 93631: When new panels are added to the record view layout while configuring the dropdown-field-based views in Studio, changing the panel label may improperly update the label of the other new panels.
• 93359: In certain circumstances, installing packages via Admin > Module Loader may fail due to an Elasticsearch error.
• 93055: Dropdown values with spaces in the display label cannot be moved into the Available Values column in Admin > Tile View Settings.
• 92217: The texts in the Product Catalog dashlet may not display properly making it hard to read.
• 92063: When campaign test emails are sent, users may notice unexpected issues with certain subpanels in the module (e.g., Accounts) that the campaign emails are related to.
• 91975: Unexpected issues may occur when designing new Process Business Rules for modules (e.g., Leads, Opportunities) that are disabled for Sugar Automate in Admin > Sugar Automate Settings.
• 91893: Adding a new filter to the list view dashlet does not apply the filter to the dashlet as expected.
• 91861: In certain circumstances, subpanels in Sugar may not behave as expected or not be configurable in Admin > Studio.
• 91283: Filtering the Emails list view using the From field does not return the appropriate results as expected.
• 89878: The Forecast Bar Chart dashlet in the Forecasts module does not display any data for individual sellers.
• 89728: In certain circumstances, opening the list view Mass Actions menu does not display properly on the screen.
• 89542: For instances with 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.
• 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.
• 86774: In certain circumstances, setting the user's non-primary email address as the Reply-to address may not consistently save the configuration as expected.
• 86285: In certain circumstances, users may experience unexpected behaviors when attempting to expand 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.
• 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.
• 81382: Deleting a target list related to a large number of records may fail with an error.
• 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.

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

Feature Enhancements

• Multi-currency support:
  • Supported currencies: Monetary values across sales-i can now be displayed in British Pounds, US Dollars, Euros, Canadian Dollars, Indian Rupees, Polish Zloty, Danish Kroner, Czech Koruna, Turkish Lira, Swiss Francs, Hungarian Forints, South African Rand, New Zealand Dollars, and Mexican Pesos.
  • Real-time conversions: Non-historical monetary values are converted to the selected display currency in real time using a blend of current exchange rates.
• Improved list view for Customers, Prospects, and Opportunities:
  • Advanced filtering: You can now filter list and grid views with most analysis, standard, and custom fields.
  • Adding columns: You can now add most analysis, standard, and custom fields as additional columns to list views.
• Export enhancements:
  • Surfacing record assignment: Opportunity and alert exports now include the user assigned to each record in the export file.
  • Larger exports: Full Picture, Variance, Matrix, and Sales vs. Gaps inquiry export files now support up to 100 columns and 100,000 rows.
• Expanded inquiries search: Searching inquiry reports now searches all rows in the report, rather than only the visible rows.

This section describes the feature enhancements and fixed issues available in this release of the Intelligence add-on. For more information about AI, refer to the AI documentation.

Feature Enhancements

• Intelligence add-on is now built into Sugar: The Intelligence add-on is now enabled by license key for SugarCloud customers and updates are no longer delivered via a module loadable package.

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

Fixed Issues

• 98024: A Sugar Connect user's related profile record was erroneously missing from the database, causing the User Management page in the Sugar Connect tenant to be unusable when the Sugar Connect user was deleted. We have addressed this issue to ensure that when an issue arises with a user profile, the tenant will remain in working order and the user can be deleted from Sugar Connect.
• 97849: In the Sugar Connect sidebar, users were erroneously able to create and edit campaign records, which is a legacy module and not supported by Sugar Connect. The problem has been addressed by redirecting users to Sugar to create and modify campaign records.

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

• Search across all lists in Email Builder: You can now search across all lists at once within Email Builder when selecting recipients, making it easier to find the people you wish to send to.
• Email template type consolidation: The three email template types have been merged into a single view, with a Type field added to accurately reflect each template type.
• All unsubscribes shown in the Buyer’s Journey: When viewing a contact or lead, the Buyer’s Journey now shows all unsubscribes, regardless of how the customer unsubscribed.
• Additional support added for Email Builder 2.0 Advanced Testing: Email Builder 2.0 Advanced Testing now supports the following clients: Android 13 Gmail App, Apple Mail 16, iPhone 16 Gmail App, iPhone 16, iPad (10th generation), Gmail App for iOS, Outlook 365, Outlook for Mac, and Outlook for Windows.
• Legacy modules use new email templates: Forms, listeners, and scoring actions now use Email Builder 2.0 email templates to support the ongoing modernization of Sugar Market.

Fixed Issues

• 98126: Email Builder 2.0 Advanced Testing support has been discontinued for the following clients: Android 6, Apple Mail 15, Gmail App for iOS, iPad (Retina), iPhone 11, iPhone 12, iPhone SE, Outlook for iOS, and Windows 10 Mail.
• 98125: The Market iframe in SugarCRM did not properly respect the ordering of nurtures a contact has participated in by nurture name, status, and created date. This has been corrected by removing the legacy nurture endpoints, and results now return as expected.
• 98121: Access to the legacy Nurture Builder has been removed to support the deprecation of older technology stacks and encourage usage of the modern Nurture Builder.
• 98115: The terminology in Email Builder 2.0 was inconsistent with the rest of the product. Minor edits have been made to labels to ensure clarity and consistency across the application.
• 98112: When a user added a list to either the Include or Exclude section, the same list still appeared in the Lists search results. This has been fixed so that once a list is added, it no longer appears in the search results.
• 98091: The captcha was not compliant with the General Data Protection Regulation (GDPR) in the European Union. This was changed, and now the captcha is compliant.
• 98090: When setting up the connector between Sugar and Sugar Market, the terminology between the two configuration pages was inconsistent. The field "Organization Name" has been removed to reduce confusion.
• 98087: Accounts created from anonymized web traffic data were only viewable to administrators because they were incorrectly marked as OwnerID = 0, which is invalid. This has been corrected so that accounts are viewable by users based on their roles, and records are assigned to OwnerID = 1 when no other user is set.
• 97968: When slider fields were marked as required, adding a slider to a form prevented response submissions. The Required option is not necessary and has been removed, and forms now submit as expected.
• 97383: Using a dynamic reply-to address showed the correct name but not the correct email address, resulting in replies going to the wrong inbox. This issue has been fixed, and the correct reply-to address is now used.
• 90436: When managing report subscriptions, Sugar Market users occasionally could not see their own subscriptions or see subscriptions from other users. This has been fixed to ensure the specific user’s ID is referenced when accessing subscriptions, and it now behaves as expected.

This section describes the feature enhancements, fixed issues, and known issues in this release of the SugarCRM mobile app. For more information about the app, refer to the SugarCRM mobile app documentation.

Feature Enhancements

• Open links in the app: When you tap a link to a Sugar record in Sugar 25.2 or higher from a mobile device (e.g., a link in an email), it now opens the record directly in the SugarCRM mobile app instead of in your device's browser.
• Smart guide activity improvement: When viewing a smart guide, you can now tap anywhere on an activity to open it instead of just the name, making navigation simpler and faster.
• Timeline usability in poor service: The timeline view has been improved to allow you to filter or search immediately rather than waiting for the timeline to load first, enabling you to find what you need quicker, especially with a slow connection.
• iPhone dynamic island in landscape mode: If iPhone users rotate their device to view the SugarCRM mobile app in landscape mode, the app now adjusts its size to not overlap the dynamic island.

Fixed Issues

• 97769: If a user with read-only access to the Teams field created an opportunity with revenue line items, they encountered an error. We have addressed this so that users can now consistently create opportunities without errors.
• 96753: Certain fields (e.g., Account Name) were not allowed to be sorted in the SugarCRM mobile app's list view. Now, the affected fields are allowed to be sorted in the list view.

Known Issues

• 98022: It is not possible to download file attachments on cases using the SugarCRM mobile app.
• 97121: Users are periodically forced to refresh while using the app to receive new admin configuration changes when there have not been any configuration changes.
• 96872: If an email is implicitly related to a record (e.g., an account), users may encounter an error when viewing the email from the record's Emails subpanel using the mobile app.
• 94981: The caller ID feature may not display the pop-up identifying Sugar records on incoming calls on certain device models or on certain networks.
• 92512: With offline mode enabled, refreshing a filtered list view of favorited records does not update the list to reflect records that have been unfavorited since the last refresh.