Resolved issues

This section includes the list of issues resolved during the most recent releases. For resolved issues for previous releases, refer to online documentation for version 23.11 at Resolved issues.

Version 25.05

CRM-2126

Fixed an issue where schedule items that were initially synchronized with Microsoft Exchange calendar and were subsequently assigned to a template that explicitly disables synchronization with Microsoft Exchange, were still synchronized with Microsoft Exchange.

CRM-2499

Previously, applying a filter that used an IF() calculated field (such as IF('Close Year'=2024 ,'Actual Amount', 'Expected Amount') > 1) would cause an unexpected SQL error and prevent the report from running. This issue has been resolved.

CRM-2948

Previously, users without the mda:OpportunitiesEnabled privilege could still see the Opportunities workspace, as well as the related tabs, badges, and reporting fields, which contradicted the intended permission behavior. This issue has been resolved.

CRM-2973

Previously, when an opportunity was deleted, the “Has Opportunity” badge was still displayed on the banner for the contact. This issue has been resolved. The badge now disappears as expected once the opportunity is removed, improving accuracy and visual clarity across contact records.

CRM-3057

Previously, attempting to create a new schedule item from the Schedule workspace in Month view could result in a “Type mismatch in vector-ref” error under certain conditions, such as after a UI reset. This has been fixed. Users can now launch the schedule item creation dialog without encountering this error, and the item will default to today’s date.

CRM-3193

Previously, deleting one calculated field from a report containing multiple aggregate calculated fields could result in an unexpected error when navigating collections. This issue has been resolved.

CRM-3279

Previously, when editing a recurring activity using the “This and all following” option, updated names did not appear in the Latest Activities tab until a manual refresh was performed. This issue has been resolved.

CRM-3363

Previously, SLM records with a target date matching the report’s end date (for example, 0 days until target) were incorrectly excluded from the predefined SLM Touches Report unless the “Include Overdue Touches” option was enabled. This behavior led to incomplete reporting for users who expected same-day touchpoints to be included.

With this update, 0-day targets are now treated as valid for the entire day, ensuring that such records are included in the report even when “Include Overdue Touches” is unchecked. This change aligns with user expectations that same-day targets are not yet overdue.

CRM-3496

Previously, searching in the Period filter chip on the Service Level Management workspace resulted in an unexpected error. This issue has been resolved.

CRM-3511

Previously, non-administrative users were able to access and export sensitive Entitlements data through user reports, despite not having access to the NexJ Admin Console. This has been resolved.

CRM-3598

The Maximum Streaming Error Count field is now displayed in NexJ SysAdmin Console for Exchange Online synchronization targets.

CRM-3692

Previously, when scheduling an item assigned to another user, the system incorrectly checked for conflicts against the current user’s calendar instead of the calendar of the user in the Assign To field. This issue has been resolved.

CRM-3695

Previously, if a report contained only a string-based calculated field, it would fail to execute and throw an unexpected error. This issue has now been resolved. Reports using calculated string expressions as their sole field now run as expected without error.

CRM-3697

Previously, after refreshing the browser when creating or editing dashboards on the Reports workspace, settings that are defined in NexJ SysAdmin Console were sometimes not initialized. This caused fields that should have been hidden, such as those controlled by reporting email configuration settings, to incorrectly remain visible when creating or editing dashboards. This issue has been resolved.

CRM-3731

Previously, exporting a report in the Detail (Excel) format that included a calculated field caused the export to hang and never complete. This also impacted scheduled exports and share by email functionality when Detail (Excel) format was selected. This issue has been resolved.

CRM-3734

Previously, a data volume exception prevented the server from starting when there were more than 4096 saved filters or lists for the entire deployment. Now, the error only occurs if a single user has more than 4096 filters or lists with the security code set to "owner" or there are more than 4096 filters or lists that have a security code of “public” across the deployment.

Note: If this error occurs, you must override the query read limit until the number of saved filters or lists have been reduced.

CRM-3894

Previously, when using the Import workspace and selecting Process Selected or Process List during a lead import resulted in no leads being created, despite the process appearing to run. This has been resolved by removing the “process” options for leads imports, aligning with the intended behavior and preventing confusion.

Version 25.02

CRM-2166

Previously, grouping some date values by week sometimes resulted in incorrect grouping. This issue typically occurred at the beginning or end of a calendar year. For example, Jan 1, 2027 was previously incorrectly placed into “Week of Jan 3, 2027” rather than “Week of December 27, 2026”. This issue has been resolved.

CRM-2747

Previously, the SLM report included data beyond the selected date range, displaying full months instead of limiting results to the specified dates. This issue has been resolved.

CRM-3020

Previously, the reseeding process for reports failed if there were any inactive users with saved report settings. This issue has been resolved and inactive users are now excluded from the seeding process.

CRM-3096

Previously, upgrading an implementation with over 4096 saved filters resulted in an error related to “nexj.core.runtime.DataVolumeException”. This issue has been resolved and the error will no longer occur regardless of the number of saved filters.

Note that similar issues may still occur in other circumstances, for example on startup or when filters are selected. If this occurs, please continue to override the query read limit for the data source in the environment file.

CRM-3218

Previously, Future Steps for activity plans were not displayed in the preview of activity plans and activities included in activity plans. This issue has been resolved and Future Steps are now correctly shown in previews.

CRM-3219

Previously, when attempting to delete a Quick Pick Enum Code that was already associated with multiple entities, an unexpected error occurred. This issue has been resolved and the appropriate error message is now displayed.

CRM-3222

Previously, when adding a new contact to a household, a warning message regarding households that are marked Do Not Contact (DNC) was displayed, even when the household was not marked as DNC. This issue has been resolved, ensuring that the warning only appears if the household is actually flagged as DNC.

CRM-3262

Previously, when creating a new report with the same name as an existing public report, the report failed to save without any error message. This issue has been resolved, ensuring that reports are properly saved, regardless of name duplication.

CRM-3274

Previously, when previewing an Activity Plan that included a read-only step (for example, a Log activity), users encountered some inconsistencies with the Delete button behavior. For example, the Delete button was visible for read-only steps when it should have been disabled. These issues have been resolved, and the Delete button is now displayed or disabled appropriately for all steps, including read-only steps.

CRM-3277

Previously, deleting an Activity Plan that included a read-only step, such as a Log activity, resulted in an “Update access denied” error. This issue has been resolved, allowing Activity Plans to be deleted, even if they contain read-only steps.

CRM-3289

Previously, after a recent upgrade, name attributes were removed from the report field selection search, although they were still available in filters. This issue has been resolved, restoring the ability to search for name attributes when adding fields to reports.

CRM-3377

Fixed an issue where updating the level of system logging using the SysAdmin Console at run-time could result in an unexpected error.

CRM-3410

Previously, adding multiple attachments to a record where at least one of the attachments was an invalid file, sometimes caused the application to become unresponsive. This issue has been resolved.

CRM-3473

Previously, errors occurred when users were filtering search results where the filter field values contained strings that could be used for relative date expressions, for example, the string “day” included in the city search for “Daytona”. This issue has been resolved and filter field values can now safely include keywords such as “Day”, “Week”, “Month”, “Quarter”, “Half”, or “Year”.

CRM-3509

Previously, when searching for an attribute in the Add Filter picker dialog while creating a report, the results included some unrelated associations and irrelevant fields. This issue has been resolved, ensuring that only the relevant fields and associations are displayed, based on the search criteria.

Version 24.11

CRM-377

Previously, if an activity status enumeration (for example, “No Response,” “Restarted”) was deactivated using the Admin Console, this did not remove it from the activity status picker when a user was updating an activity in NexJ CRM. This issue has been resolved, and deactivated statuses no longer appear in the list when adding or updating activity statuses.

Note: Administrators should ensure that no active objects are using a status before deactivating it.

CRM-1531

Previously, when the currencyConversion flag was disabled and a currency field referred to the system currency, filters incorrectly used converted values for comparison instead of the system currency values. For example, a filter like Actual Amount greater than 2 would incorrectly compare a converted value (for example as EUR 3.79) instead of the original system value (for example, CA$1.00). This issue has been resolved, and filters now correctly compare values based on the configured currencyConversion setting and system currency.

CRM-1769

Previously, on the Service Level Management workspace, the Schedule Touch button did not work when attempting to schedule an activity for custom touch types, such as Strategic Partner Review. This issue has been resolved, and the Schedule Touch button now functions as expected for both out-of-the-box and custom touch types.

CRM-2084

Previously, when the user’s currency was changed on the Localization in the User Preferences dialog, the value for the Convertible Currency custom fields in reports did not update accordingly, even though the currency itself was correctly updated. This issue has been resolved, and both the currency and the value for Convertible Currency fields in reports now reflect the current user’s preferred currency.

CRM-2485

Previously, during JVM crashes or OOM situations, a heap dump was not generated if the default location did not have write permissions or had insufficient storage space. This issue is resolved by using the new environment variable JAVA_HEAPDUMP_PATH to indicate where the heap dump should be saved.

CRM-2487

Previously, second Y-axis in a report chart was not always visible while the report was being edited. This issue has been resolved.

CRM-2516

Previously, when adding a “Do Not Contact” (DNC) contact to an Activity Plan, the DNC prefix was shown in the contact picker but not in the “For” field after the contact was selected. Now, the DNC prefix will consistently appear in the “For” field for both Contacts and Households, ensuring better visibility of DNC status when creating or managing Activity Plans.

CRM-2517

Previously, when adding a Schedule Item as a step in an Activity Plan for a “Do Not Contact” (DNC) contact, a warning correctly notified the user that the DNC contact would be removed. However, the contact was still being added back when the assigned step was edited. This issue has been resolved, and DNC contacts are now removed from the Schedule Item as intended.

CRM-2631

Prior to this release, when a calculated field contained a PERCENTOF() function applied to a Currency field, using that field as a sort field resulted in incorrect ordering of the report data under certain circumstances. This issue has been resolved.

CRM-2634

Fixed an issue where a call to getUser() during a seeding step, typically performed when upgrading to a newer version of CRM, could fail to locate the NexJ System User (nexjsa).

CRM-2649

Previously, when currency conversion was enabled, sorting a mixed-currency list of opportunities by Expected Amount would result in incorrect sorting based on raw numeric values rather than converted amounts. This issue has been resolved, and the sorting now correctly accounts for currency conversions.

CRM-2770

Previously, under certain circumstances, users encountered a repeated “Flexmonster: Pivot cannot be drawn” error dialog when opening Ad Hoc reports or dashboards, which required users to click the OK button on the dialog multiple times before the report would load. The issue has been resolved.

CRM-2904

Previously, attempting to clone a report with a filter referencing a large number of enumeration values failed, resulting in an “Invalid Filter. The value of Filter must be up to 8192 characters long” error. This issue has been resolved, allowing reports with large enumeration filters to be cloned without encountering this character limit error.

CRM-2908

The nightly sync job to update the global search index was conflicting with other nightly batch jobs. To remove the conflicts, the default value for the JSON configuration attribute nightlyBatchStartTime was changed to 10:30 PM in the organization’s time zone (ignoring DST).

CRM-2949

Previously, when a campaign was cancelled or deleted, the “Has Campaign” badge continued to be displayed on a participant’s profile. This issue has been resolved.

CRM-2953

Previously, when changing the report currency in a Deals report that included the PERCENTOF('Expected Amount', 'Stage') field, an unexpected “Divide by zero” error would occur. This issue has been resolved, and currency changes are now processed correctly, maintaining the expected 100% value for each stage in the PERCENTOF field.

CRM-2976

Previously, when a report title exceeded 64 characters, the generated report identifier would also exceed the limit, causing a validation error. This issue has been resolved by limiting the generated report identifier to 64 characters, based on the beginning characters of the report title.

CRM-2978

Previously, when attempting to clone reports that used enumeration filters, an unexpected “Type Mismatch” error occurred. This issue was caused by incompatible formatting of enumeration filter values in older reports. The issue has been resolved, and reports with enumeration filters can now be cloned successfully.

CRM-3135

When the Enable sensitive attribute masking attribute was enabled in the Admin Console under Statistics > nexj.finance > Administration, all attribute names and values were incorrectly hidden from the system log output of any RPC calls. This issue has been resolved and enabling this attribute only masks the values of select sensitive attributes for which logMask property was set in the CRM model.

Version 24.08.0.1

CRM-2976

Previously, when a report title exceeded 64 characters, the generated report identifier would also exceed the limit, causing a validation error. This issue has been resolved by limiting the generated report identifier to 64 characters, based on the beginning characters of the report title.

Version 24.08

CRM-27

When some navigable entity-type fields (for example, Household) were added to a report as an association of another entity, the navigation link occasionally did not bring the user to the correct CRM screen. This issue has been resolved.

CRM-992

The "Clear queue" functionality on the Object Queues tab of the System Admin Console has been modified to function more efficiently with high depth queues.

CRM-1144

Fixed an issue where a NullPointerException could occur while handing the original exception scenario, therefore masking valuable troubleshooting information in the logs.

CRM-1229

Fixed an issue where push notification connection was not properly shut down with the server.

CRM-1289

Updated wording used on the Add Filters for <Association field> dialog to better reflect the fact that additional sub-filters could still be applied.

CRM-1336

Fixed an issue where a cloned dashboard template could lose reference to its reports after the environment was upgraded to a later version.

CRM-1341

Fixed an issue where the value of Probability was formatted as a decimal and not as a percentage on Summary tab.

CRM-1482

Fixed an issue where the Date and Time picker dialog was missing the OK and Cancel buttons when the UI was viewed at 175% scale.

CRM-1514

Previously, when adding a report to the dashboard, using the quick search to look up a report name incorrectly limited the list of reports displayed. This issue has been resolved.

CRM-1538

Fixed an issue where the hideSpecificFilter="true" subject area configuration flag applied to association fields did not take effect in dashboards.

CRM-1717

Fixed an issue where referencing a Timestamp attribute in a calculated field formula (for example, Create Time) resulted in a Date format value.

CRM-1747

Previously, when currency conversion was enabled and a currency field was added to a calculated field formula, sorting on the resulting calculated field could result in an incorrect sort order. This issue has been resolved.

CRM-1763

Fixed an issue where a report with a lot of columns could extend beyond the edges of the screen when being added to a dashboard.

CRM-1765

Fixed an issue where disabling navigation for entity-type association fields did not work.

CRM-1782

Previously, when a predefined report was selected from the contact record from the household member list in the Households tab on the Contacts workspace, an error was being displayed in relation to the householdMembers attribute. This has been fixed.

CRM-1809

When a calculated field is added as a grouping on a bar chart, the values are now sorted in the correct order on X-axis, as expected.

CRM-1858

Fixed an issue where it was possible to hide all of the chart legend categories causing the chart to enter a bad state.

CRM-1916

Fixed an issue where the Max field length system parameter did not get applied to association and calculated fields when the report was exported to CSV.

CRM-1927

Previously, when a privileged report administrator executed a report as another CRM user (using the "Run As" option), navigated to the Settings tab, and then scheduled the report to be shared through email, an error was displayed if the report administrator did not have an email address configured in NexJ CRM. This issue has been resolved.

CRM-1996

Fixed an issue where entering duplicate email address values into the Email Address Targets field in the Settings tab on the Schedule card resulted in an error.

CRM-2052

Fixed an issue where adding an association filter on a dashboard could cause the dashboard to refresh prematurely.

CRM-2079

When adding the Custom Fields associated collection field to a report, you can now filter on it using the dropdown menu on the field chip. Previously, you could only do this using the Add Filters dialog. This issue has been fixed.

CRM-2088

Fixed an issue where a calculated field containing COUNT('Custom Fields') in its formula incorrectly displayed 0 when the contacts included in the report had custom fields added to the profile and when the Include all related records field was set to No.

CRM-2097

Fixed an issue where referencing CLOB attributes (for example, Bio) inside a calculated field formula resulted in an unexpected error.

CRM-2133

Fixed an issue where the colors of a chart seen in the UI could be different from those in the exported file in the PNG or PDF format.

CRM-2160

Fixed an issue where the Display related collection data inline toggle was not set to the correct value if the report was being viewed by an administrator running the report as another CRM user.

CRM-2203

Previously, when currency conversion was enabled and a calculated field referenced both a Currency field and an Enumeration field in its formula, an unexpected error occurred. This issue has been resolved.

CRM-2254

Fixed an issue where an error during sharing a report by email caused the UI to become unresponsive.

CRM-2331

Fixed an issue where Task notes were occasionally not displayed appropriately in the Activities tab for some households.

CRM-2338

Fixed an issue where adding a period (".") or comma (",") character in the caption of a calculation used in the chart Y-axis caused the visualization to not render.

CRM-2465

Previously, the filter chip used to search for household names was incorrectly labeled “Last Name”. The filter label has been changed to "Name" to more accurately reflect what is being searched

CRM-2467

Previously, if a user was locked by Keycloak and then fields in that user's record were edited using NexJ Admin Console, then the user would be unlocked. This issue has been resolved.

CRM-2472

Fixed an issue where including an Object ID of an association in the report prevented the report from being exported to PDF.

CRM-2478

In a previous release, some PDF exports that did not fit on one page displayed each report column on a separate page. The new "Fit to page" option for Overflow Page Order can now be specified on the Settings tab for the report in order to include all report columns on the same page.

CRM-2518, ECRM-29146

The pushrd.sh and pushrd.bat scripts were updated to prevent unnecessary illegal reflective access operation warnings.

CRM-2564

Fixed an issue where a template containing calculated fields could not be used to create new reports.

CRM-2576, AFL-4196

Fixed an issue where updating a leap year date value to another value did not work.

CRM-2580

Fixed an issue where using the @related: operator as a part of the Global Search query resulted in a syntax error.

CRM-2613

Fixed an issue where the default sort field (Full Name) was not applied on Contacts reports.

CRM-2630

Fixed an issue where a "(specific)" filter dialog applied on a dashboard did not display the Value search field.

CRM-2643

Fixed an issue where an unexpected error was displayed after a scheduled report was exported if one or more of the target email addresses were not valid. All valid email recipients still got their copy of the report.

CRM-2663

Previously, when a user created a schedule item for a targeted activity plan and the schedule item had a non-default duration, an error was displayed. This issue has been resolved.

CRM-2684

Fixed an issue where multiple fields could appear to be in focus after the tab key was used to navigate across a form.

CRM-2699

Previously, Activity Status filters were not showing all possible values. This issue has been resolved.

CRM-2742

Fixed an issue where the Summary and Visualization tabs could appear empty when a template report is viewed for the first time.

Version 24.05

CRM-405, CDM-5006, CRM-1796

Related opportunities data for household members now exports as expected to CSV files.

CRM-1195

Fixed an issue where a calculated field formula that contained the COUNT('For') function incorrectly included entities hidden by the data visibility rules in the result.

CRM-1264

When the Date of Birth field is referenced in a calculated field formula, its value could previously be off by a day, depending on the user's time zone. This issue has been resolved.

CRM-1354

When a DATEADD() function was used in a calculated field formula and the resulting value crossed the DST change date, an incorrect date value was previously be returned. This issue has been resolved.

CRM-1486

An issue that caused you to receive an unexpected error if you sorted your activity items by due date has been resolved.

CRM-1557

Previously using the $url tokens in notification emails under certain circumstances directed the user to the incorrect version of the product. This issue has been fixed.

CRM-1569

On the Service Level Management workspace, the Period filter chip now displays periods in the user's time zone and not in UTC.

CRM-1632

Fixed an issue where certain chart types (for example, the Column Line chart) did not have a consistent look when exported to PDF or PNG or when viewed in the UI.

CRM-1682

The “Unsubscribe” link for emails that is included at the bottom of an email for a user when they are notified about a task being assigned to them was not working. This has been fixed.

CRM-1687

Fixed an issue where users in the "Australia/Eucla" time zone were not able to access the NexJ Reporting workspace.

CRM-1751

Previously when the report currency was changed from its default value and a filter on a currency field was added, it was possible for the data in PDF export to not match the UI and the CSV export. This issue has been resolved.

CRM-1771

Fixed an issue where adding a calculated field with PERCENTOF() function could result in an error if the grouping field used as the function parameter contained more than 500 distinct values.

CRM-1772

Previously, clicking on a nested collection field on the Configure Filters dialog potentially caused the UI to enter a bad state and required the browser window to be reloaded. This issue has been resolved.

CRM-1921

Previously, when a dashboard was initially configured to include report components from multiple subject areas and then components of only a single subject area were left in the dashboard, trying to add a filter failed with an error. The issue has been resolved.

CRM-1923

Previously, when the Include all related records field was set to "No" and a calculated field contained an aggregate function on a related currency collection field, the result of the aggregate function was incorrectly calculated. This issue has been resolved.

CRM-1930

Fixed an issue where data values were not included in the legend of a funnel chart when exported to PDF or PNG.

CRM-1933

The PERCENTOF() function previously returned incorrect results when it was applied to a currency field for which currency conversion was enabled and the source values were stored in multiple currency units. This issue has been resolved.

CRM-1934

Fixed an issue where a sub-grouping on the Summary tab of a report displayed “(blank)” value incorrectly when viewed from a dashboard.

CRM-1940

Fixed an issue where NexJ Model Server provided HTTP 404 response in place of HTTP 403, despite “HTTP Forbidden Response Enabled” flag set to True in the Environment configuration.

CRM-1950

Fixed an issue where the NexJ Server script responsible for ending the process that failed with OutOfMemoryError did not generate a head dump.

CRM-1956

Fixed an issue where starting GlobalSearchSyncBatchJob with empty parameters resulted in java.lang.NullPointerException.

CRM-1998

Fixed an issue where a scheduled report execution did not recover gracefully in case an underlying error occurred.

CRM-2004

Fixed an issue where the "Previous scheduled report execution failed on : Invalid Notification" message was incorrectly displayed if the name of the report and the combined recipient list was longer than 255 characters.

CRM-2055

Fixed an issue where the “>” symbol did not display correctly in Summary columns headers of the PDF export of a report.

CRM-2058

Fixed an issue where the report components added to a dashboard lost their specified caption and description values when expanded.

CRM-2091

Fixed an issue where a dashboard containing a component of a report that the current user is unable to access due to missing privileges, would incorrectly appear empty and an error was generated in the JavaScript console.

CRM-2098

Previously reports containing an association field that referred to a large data collection could fail with an error during an export to CSV. This issue has been resolved.

CRM-2102

Fixed an issue where a report containing a grouping by week on a timestamps field (for example, “Expected Close”) could display misleading grouping data.

CRM-2108

Fixed an issue where a report or a dashboard could not be shared by email to a list of recipients delimited by the semi-colon (“;”).

CRM-2128

Entities that should not have been visible to users who did not have access to the relevant rep code were visible. This has been fixed.

CRM-2155

Fixed an issue where setting businessHourStart parameter to 0, in order to effectively disable the calendar shading, incorrectly resulted in 8 a.m. as the start of day.

CRM-2164

Fixed an issue where the GlobalSearchSyncBatchJob did not report on its start and end times.

CRM-2221

Fixed an issue where selecting both an associated field (for example, “Author”) and its name attribute (for example, “Author > Full Name”) resulted in a blank column added to the report’s CSV export.

CRM-2254

Fixed an issue where an error during sharing a report by email caused the UI to become unresponsive.

CRM-2337, CRM-2348

Fixed an issue where a report that contained a grouping on timestamp fields (for example, “Expected Close”) would generate an unexpected error if viewed by the user in UTC-8 time zone.

Version 24.02

CDM-5302, CRM-23

Prior to this release, when currency conversion was enabled in CRM, if a report included associated fields with currency values and had filters on such fields, then the total number of related records was inaccurate. This issue has been resolved.

CRM-24

Fixed an issue where excluding a field from the configuration of an association also incorrectly removed the same field from the main subject area.

CRM-25

Fixed an issue where currency conversion was not performed on the currency fields added to a report in the preview mode, while the report was being edited.

CDM-5380, CRM-36

When a currency field (for example, "Expected Amount" for a Deal) is added to a report, the amount is now accurately displayed when the System currency unit is different from the currency unit configured in CRM for that field.

CDM-5435, CRM-42

Previously, when a filter was added for an association attribute (for example, Company > Employees) that is also used in a calculation on Summary tab, the calculation displayed incorrect results. This issue has been fixed.

CRM-195

Unexpected run-time errors that occurred during the evaluation of a calculated field formula previously result in the NULL (empty) value displayed for the affected field. This issue has been fixed.

CRM-348

Fixed an issue where an error occurred if an associated field (for example, “Related Opportunities”) and its specific name attribute (for example, "Related Opportunities > Description") were both added as grouping fields on Summary tab. A new validation logic was added to prevent such a scenario from happening.

CDM-5054, CRM-415

Previously, you could not apply multiple filters fields one by one to a dashboard for ad hoc reporting as adding a new filter field erased the filter field that had been previously added. This issue has been resolved.

CRM-430

Tasks for clients secured by rep code were visible by other users that did not have access to that rep code. This has now been fixed.

CRM-454

An issue where the banner carousel becomes unresponsive when the DPI scaling is at 175% or higher has been resolved.

CRM-584

Fixed an issue where cloning a report that contains a large Enumeration field could fail with an error.

CRM-627

Fixed an issue where adding a filter on a calculated field whose formula referenced multiple currency fields (for example, Expected Amount > Actual Amount) could produce incorrect results.

CRM-748

Fixed an issue where the data displayed in SLM workspace did not refresh if the user navigated away and back to it.

CRM-913

Additional date filter validation has been added when using the between operator to verify that both To and From values are specified.

CRM-993

Fixed an issue where the values of Calculated Fields that referenced currency fields with mixed currency unit values could be incorrectly computed if currency conversion was enabled.

CRM-1170

Previously, when any column had been sorted in the "My Contacts' Recent Activities" tab on the Home workspace, the related report was failing to run. This has been fixed.

CRM-1251

Fixed an issue where unexpected errors could be displayed in the UI if the "Save" button is clicked too quickly after "Edit" and the report configuration does not fully load.

CRM-1268

Fixed an issue where it was not possible to schedule a dashboard update without also sharing it by email.

CRM-1282

Resolved an issue where the server potentially logged a failure to create an Elasticsearch index when run in a clustered setup.

CRM-1306

Previously, when the order of opportunity stages had been customized and then a reseed or redeploy was performed, the stages were reverted to the default ordering. This has now been fixed.

CRM-1355

Fixed an issue where using an "equals" date filter on a calculated field containing DATEADD() function could result in matching records excluded from the report.

CRM-1357

Fixed an issue where EntitlementHierarchyRebuildBatchJob that runs on a regular basis could fail with a DataVolumeException.

CRM-1382

Resolved an issue where a batch job that runs periodically and cleans up expired report exports could select too much data for processing and result in high TempDB utilization on the database server.

CRM-1414

Addressed an issue where sorting on a currency field in a report could produce incorrect results if the field contained values originally saved in different currency units and if currency conversion was enabled on the field.

CRM-1454

Addressed an issue where report fields that were explicitly disabled from being sortable (sortable="false" flag was set) were still listed in the Sort Field dialog.

CRM-1457

Fixed an issue where creating a new report from a pre-configured template that contains calculated fields resulted in those calculated fields incorrectly removed from the report definition.

CRM-1580

Previously, testing for Entity Import was incorrectly defaulting to USA. This has been fixed.

CRM-1628

Previously, recreating did not retain all privileges for the Administrators privilege group. This has been fixed.

CRM-1685

Previously, an unexpected error occasionally occurred when a user clicked on "Save filter" under Activities tab for an entity. This has been fixed.

CRM-1714

Fixed an issue where adding a nested collection association filter could result in the report CSV export to fail with an error.

CRM-1751

Previously, when the report currency was changed from its default value and a filter on a currency field was added, it was possible for the data in PDF export to not match the UI and the CSV export. This issue has been resolved.