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 26.08
CRM-47
Improved the visibility of long field names in report association paths by ensuring partial text and tooltips are displayed when space is limited.
CRM-278
Updated the Task workspace to replace the Call Record icon with a clickable description link that opens the preview drawer instead of the edit dialog.
CRM-1345
Resolved a defect where entity coverage changes made in the CRM UI were not being recorded in the Audit Trail.
CRM-2474
Updated the Reset filter action in the Reports workspace to retain default filter chips while clearing their values.
CRM-2924
Resolved an issue in the NexJ SysAdmin Console where the previously enabled additional logging level configuration could not be removed from the cluster nodes without a specific sequence of status synchronization and restarts.
CRM-3877
Fixed an issue where date/time aggregations in reports were exported as numeric values instead of timestamps when grouped by a Boolean false value.
CRM-4032
Improved validation messaging in the Calculated Fields dialog to correctly identify invalid attributes instead of showing unrelated aggregation errors.
CRM-4120
Summary and visualization data in the Reporting workspace now correctly respect the Include all related records option even when a parent association path is not explicitly defined.
CRM-5591
Adjusted the positioning of the Floating action toolbar button in the Reports Summary tab to prevent it from obstructing navigation controls.
CRM-5653
Previously, meeting attachments were lost in Microsoft Outlook when a meeting pattern was updated from non-recurring to recurring using NexJ CRM, when synchronized using Microsoft Graph API. This issue has been resolved.
CRM-5928
Updated the contact import grid to prevent empty cells in the Match name column from being clickable.
CRM-5960
Fixed a display issue in the schedule item preview pane where “All Day” events incorrectly showed the end date as the following day.
CRM-6125
Previously, when exporting a Contacts subject area report using the Details (Excel) option, the Date of Birth values sometimes appeared one day earlier than shown in the NexJ CRM interface. This issue has been resolved.
CRM-6149
Previously, schedule items created in NexJ CRM by a user who was not enabled with Exchange Synchronization (using either Exchange EWS or Graph API) did not synchronize to Outlook for user participants that were enabled with Graph API synchronization. This issue has been resolved.
CRM-6175
Previously, for scheduled dashboards that used filters on associations, the emailed PDF export omitted some dashboard items that appeared in the CRM user interface. This issue has been resolved.
CRM-6241
Previously, for recurring meetings synchronized using Microsoft Graph API, attendee responses for individual occurrences (Tentative, Decline, or Accept) were not always reflected correctly on the Attendees tab for the activity in NexJ CRM. This issue has been resolved.
CRM-6244
Previously, attendees that did not exist in NexJ CRM who were added to Outlook meetings did not appear under External Contacts for the corresponding meetings in NexJ CRM when synchronized using Microsoft Graph API. This issue has been resolved.
CRM-6325
Previously, in environments where synchronization was performed using both Graph API and Exchange EWS, creating a schedule item in NexJ CRM as a Graph API–enabled user and inviting an EWS‑enabled participant could result in duplicate schedule items. This issue has been resolved.
CRM-6327
Previously, when a user with Graph API synchronization enabled updated a schedule item in NexJ CRM to change it from non-recurring to recurring, the original meeting item was not deleted in Outlook as expected. This issue has been resolved.
CRM-6347
Previously, in an environment using Graph API for synchronization, removing an external contact from a meeting in NexJ CRM did not remove that external attendee from the corresponding Outlook meeting for the organizer. This issue has been resolved.
CRM-6456
Previously, clicking in the empty space after the last table header column (such as after the Date of Birth column on the Contacts workspace with default column choices) caused an empty green focus indicator to appear. This issue has been resolved.
CRM-6463
Previously, in the Reporting workspace, the Up Arrow and Down Arrow keys stopped working for navigating subject areas in the Create Report dialog after keyboard focus left the dialog and then returned to it. This issue has been resolved.
CRM-6483
Previously, an “unknown attribute” error occurred when selecting the Data Migration – Interactions Associations report. This issue has been resolved.
CRM-6499
Enforced privilege requirements for editing public reports, ensuring that users can no longer modify reports they created if their management privileges have been revoked.
CRM-6511
Previously, an unexpected error occurred in the Batch Processes workspace when attempting to sort by the Name column after performing a batch action (such as Print Document or Send Email) on Leads. This issue has been resolved.
CRM-6595
Removed an extraneous 12-hour shift at the end of the Person'getNextBirthday event to ensure accurate birthday calculations.
CRM-6596
Fixed a validation error that occurred when saving a schedule item after modifying the end date to be before the start date and then correcting the start date.
CRM-6618
Fixed a navigation issue in the Leads workspace where drilling down into a lead could intermittently open a different record than the one selected.
CRM-6814
Fixed an issue where customizing AFL theme colors could cause server startup errors and UI layout corruption. In addition, theme validation logic has been updated to handle color substitutions correctly and provide more detailed error reporting for theme conflicts.
CRM-6973
Fixed a bug where report previews would fail with a misleading visibility error due to incorrect where-clause assumptions in the ReportView metadata.
CRM-7066
Fixed an issue where pressing the Delete key on a note in the Summary tab incorrectly opened a confirmation dialog with the wrong message and does not delete the note.
Version 26.05
CRM-74
An unexpected error observed when clicking on the Account Plan picker in the Related tab when creating or editing activities no longer occurs.
CRM-250
The Batch Processes workspace now shows the correct count for total, completed, and processed records when merging entities.
CRM-327
Fixed state and province values appearing blank when editing an address, caused by incorrect format in sample data (for example, "ON" instead of "CAN_ON"). A data fix script is provided for existing environments.
CRM-373
Previously, when an entity merge failed, clicking on the batch process description displayed "Information about Merge Entity batch processes is not available" instead of the actual error details. The Batch Processes workspace now correctly displays error information for failed merge operations, including both the source and target entities.
CRM-2149
In reports, the Include all related records option was not respected when an aggregate function referenced an enumeration field (such as COUNT of Activities: Status), causing the count to include all records instead of only filtered ones. The aggregation now correctly applies the filter when the calculated field references an enumeration.
CRM-2187
Previously, using the "Limit number of displayed groups" (Other groupings) feature in report visualizations caused an error when the same field was used for both the X-axis category and chart grouping. The aggregation logic now correctly handles this scenario.
CRM-2208
Detail Report, Interaction Report, and Briefing Book reports now correctly respect ACL security and no longer display company names hidden by rep code access limitations.
CRM-2213
The Company column in the Batch Processes workspace now correctly respects ACL security and hides company names users do not have rep code access to view.
CRM-2494
Previously, if the PDF export engine was not appropriately configured, then the Share Dashboard > Share by Email command would hang indefinitely with an "An export is in progress" message. The Share by Email command is now hidden when the export engine is not available.
CRM-3393
Fixed issues where users with only rpt:ReportPublicManage privilege could not view public reports and got errors when attempting to save reports. Invalid security options are no longer presented, and rpt:PublicReportView privilege is now required to view public reports.
CRM-3696
Previously, the Select a contact dialog used for the Merge into… menu item appeared to support full name search. The placeholder text for the search field has been updated to "Search by name", to clarify that only first and last name search is supported.
CRM-3880
Previously, Pixel Perfect reports incorrectly displayed time periods alongside Tasks in multiple areas including Contact Details, Opportunity, Service Request reports, Home Updated Activities, Schedule Workspace, and SLM Workspace. Time is no longer shown with Tasks in these reports, consistent with the rest of the application.
CRM-4020
When seeding system filters, pre-existing user-created filters with the same name were incorrectly overwritten, which could hide filters from users. The seeding process now detects pre-existing non-system filters with conflicting names and renames them to preserve the user's original filter.
CRM-4094
Fixed multiple UI inconsistencies in the Opportunities picker for Hold Note and Advisory Note forms, including missing column headers, missing icon column, incorrect search placeholder, and inconsistent dialog caption.
CRM-5392
In the Report Builder, association fields (for example, Company in a Contacts report) could not be added as summary aggregation calculations using the Add Field as Calculation option or the quick search. Associations can now be added as calculations through all available methods, consistent with the calculation picker.
CRM-5604
Previously, when a report's default count calculation was replaced with a custom one, the visualization Y-axis did not update automatically. This caused the Summary and Visualization tabs to hang. Now, a default value is assigned to the Y-axis when the original calculation is removed.
CRM-5748
The Dashboard export menu in the Reports workspace displayed an incorrect caption ("Full Report (PDF)" instead of "Dashboard (PDF)") when accessed from the More Actions menu. Additionally, the PDF icon on the Dashboard page export option did not match the expected icon. The caption and icon have been corrected.
CRM-5898
The Select users dialog only supports search by first or last name in the name search field. The field placeholder text has been updated to "Search by name".
CRM-6091
Previously, exporting a report to Excel failed with a null pointer exception when the Object ID field was included in the report. The export logic has been updated to correctly handle the Object ID column type, and Excel exports now complete successfully.
CRM-6092
Previously, after selecting a value from a typeahead field in a M1 or MM selection dialog, focus was incorrectly placed on the text input rather than the newly added chip, preventing the user from immediately deleting the chip. Focus is now on newly added chip after selection.
CRM-6160
Previously, when saving a new or edited schedule item, if a start date or end date validation error occurred, then correcting just one of the dates did not clear the error on the other. Now, when the user begins modifying either date, the other date is cleared as well, allowing the changes to be saved.
CRM-6163
Fixed an issue where the locale change confirmation dialog in the User Settings dialog intermittently became unresponsive due to a race condition with the alarm reminder window.
CRM-6356
The Contact Touches report now requires the new rpt:ServiceLevelViewAdmin privilege to access all SLM data. Without it, users can only report on SLM data for themselves and their direct reports.
CRM-6423
Fixed an issue where cancelling a filter popup in a picker dialog could cause subsequent confirmation dialogs to become unresponsive.
CRM-6434
Previously, the UserReminderCleanupJob batch job failed with an SQL exception (“ORA-06502: character string buffer too small”) due to a database query generating values that exceeded the buffer size. The query has been adjusted to prevent the buffer overflow, and the batch job now completes successfully.
CRM-6441
Previously, table count captions displayed "none selected" instead of using a numeric value. The caption has been updated to use a numeric value, such as displaying "117 items | 0 selected" instead of "117 items | none selected".
CRM-6598
Previously, pressing the Enter key while a dialog is open incorrectly triggered the Cancel action instead of the expected Save action. This only occurred in dialogs with customized button layouts (such as the Save and Submit button the New Schedule Item dialog). The button focus order has been corrected so that pressing the Enter key now triggers the primary Save and Submit action as expected.
Version 26.02
CRM-3235
When a user is removed from a rep code and ACLs are rebuilt, access is now revoked from child activities as well, so users can no longer see activities for entities they no longer have permission to access.
CRM-3525
Sunday is now excluded from workweek reports in the Schedule workspace for users outside of the Eastern Time Zone.
CRM-3730
Custom calculation captions that contain numbers now appear on charts exactly as entered, instead of having their digits spaced or reformatted.
CRM-3847
The hideErrorValveReport and hideErrorValveServerInfo environment properties now default to true, improving the secure default configuration of error reporting.
CRM-3896
In the Service Level Management report, the Show full notes option is now correctly dependent on enabling the Show activities option, preventing users from enabling full notes without including the related activities.
CRM-3992
Prior to this release, when a user updated the Template filter on the Opportunities workspace and set the operator to ‘equals’ or ‘no equals’ without setting the value, this resulted in an unexpected error. This issue has been resolved.
CRM-4234
Deleted companies are no longer shown in custom field values or deletion messages when the underlying entity has been removed.
CRM-5687
Global Search now correctly bolds results whose titles or descriptions contain leading or trailing spaces.
CRM-5719
JVM arguments specified in the jvm.conf file now correctly override those set in the modeld and push redirector scripts, allowing administrators to control settings like stack size and metaspace size.
CRM-5750
When the alarm dialog opens, inline dialogs such as filter field callouts and the schedule month item overflow views are now automatically closed to prevent broken, unresponsive states.
CRM-5757
Tab controls in the interface now show a proper hover background and accessible focus styling with appropriate text color in both light and dark modes, as aligned with the Material Design 3 standard.
CRM-5771
Task list selections now remain aligned with the row a user clicks, even when using large page sizes and after resorting, so the correct task is opened and edited.
CRM-5847
On Windows with Java 8, the NexJ Server (modeld) and push redirector scripts now apply the -Dsun.io.useCanonCaches=false JVM argument correctly, ensuring the intended security mitigation is enabled without relying on Tomcat fallback.
CRM-5869
The legacy Ad Hoc Report workspace and the mda:AdHocReportsEnabled privilege have been removed, so the deprecated Ad Hoc reporting features are no longer visible or assignable. Use the NexJ Reporting functionality accessed from the Reports workspace instead.
CRM-5918
In the Schedule Workspace, the View/Hide button now automatically sets to View when only one user remains, so users are not left in a hidden, empty state.
CRM-5926
The Schedule View/Hide control at the framework level now updates correctly so that when only one user is visible, the button state is refreshed and users cannot remain stuck with a hidden schedule.
CRM-5955
When drilling down to a contact's Calendar tab and then returning to the contact list, the banner now displays correctly and the Return button remains available.
CRM-5958
Saving a meeting with the Enter key now triggers the same schedule conflict checks as clicking Save and Submit, ensuring conflicts are always detected.
CRM-5961
The system no longer allows maintaining multiple active synchronization links for a user for the same calendar folder across EWS and Graph API synchronization targets, preventing infinite cloning of schedule items.
CRM-6021
Reports such as Contact Detail, Interaction, and Briefing Book reports now respect ACL security for related companies, hiding company names the user is not authorized to see.
Version 25.11
CRM-5
Previously, when filtering Contact or Activities reports against the associated Related Opportunities' actual or expected amount, the filter would incorrectly use the system currency instead of the specified filtering currency. This issue has been resolved.
CRM-81
Batch print options on lists have been changed to ensure that the UI works on mobile devices.
CRM-437
Previously, when editing a recurring schedule item's series from the preview, the preview could become blank because the schedule item was recreated and the previous item was deleted. This issue has been resolved by ensuring users can continue editing without losing context.
CRM-2760
Previously, currency-related filters did not filter data correctly for some reports in a dashboard. This issue has been resolved.
CRM-2808
Previously, when calculated field data did not relate to the grouping field data, it was not correctly not displayed in the report summary. This issue has been resolved.
CRM-2905
Previously, dashboard filters were not respected in scheduled dashboard exports or emails. This issue has been resolved.
CRM-2930
Previously, sorting on attributes did not always return the correct result for the second sorting field. This issue has been resolved.
CRM-2941
Previously, the calculated field dropdown menu did not disappear when a field was deleted, which allowed users to add nonexistent fields to grouping, filters, calculations, or sorting, causing errors. This issue has been resolved.
CRM-2954
Previously, chart details did not bring up relevant data on drill-down if chart grouping was on an associated attribute. This issue has been resolved.
CRM-3022
Previously, when the NexJ Server was deployed with JDK 11 or JDK 17, JVM statistics for CPU usage were sometimes reported incorrectly, making it difficult for users to monitor system performance. This issue has been resolved.
CRM-3101
Previously, dashboards could incorrectly show preview data after creation. This issue has been resolved by ensuring dashboards display the correct, non-preview data.
CRM-3965
Previously, entities could appear in Global Search results from an address or telecom search even if the user did not have access to the entity, potentially exposing restricted data. This issue has been resolved.
CRM-4031
Previously, if a report that only contained a calculated field was added to a dashboard, an incorrect error message would appear, preventing the report from being displayed. This issue has been resolved.
CRM-4155
Previously, Global Search showed the Opportunity subject area even for users without the mda:OpportunitiesEnabled privilege. This issue has been resolved.
CRM-4170
Previously, using the Share by Email feature in reports could cause an unexpected error. This issue has been resolved.
CRM-4213
Previously, the Select import file and Select a mapping controls appeared out of alignment if a CSV file with a long name was used. This issue has been resolved.
CRM-4220
Previously, the Import Data dialog had unclear or misaligned labels and buttons, making it harder for users to import files. This issue has been resolved.
CRM-5416
The Reports to tab of the hierarchy no longer shows redundant reciprocal relationship arrows.
CRM-5514
Previously, ARIA tags in the Business Processes tab were not valid, impacting accessibility. This issue has been resolved.
CRM-5585
Previously, reporting association paths longer than four resulted in broken reports for certain configurations. This issue has been resolved by ensuring association paths of any length are handled correctly.
CRM-5739
Previously, changing the Start Date on a task did not automatically update the Due Date, requiring users to manually adjust both fields. This issue has been resolved.
CRM-5754
Previously, dragging schedule items in the schedule workspace could leave behind selection blocks and cause the selected state to not be retained when opening the context menu. This issue has been resolved.
CRM-5771
Previously, selecting a task in a sorted task list with a large page size could result in the wrong task being selected, causing users to open or complete the incorrect task. This issue has been resolved.
Version 25.08.1.0
CRM-5618
Previously, using the Database Schema Tool in NexJ Studio to generate a database CREATE or UPGRADE script failed with an error. This issue has been resolved.
If hostname aliasing is used in your environment, ensure that the subdomain portion of the host name value matches the database host name specified on the database connection.
Version 25.08
CRM-1731
Previously, “Period” and “Touch Type” types were not properly supported in Calculated Fields, resulting in errors and unusable fields. This issue has been resolved by adding support for these types.
CRM-1825
Previously, the error banner in a dialog did not support keyboard focus or activation, impacting accessibility. This issue has been resolved.
AFL-2553, CRM-1851
The Enter key or Ctrl+Enter key combination can now be used to commit changes in NexJ CRM. For example, Enter is used for single line text fields and Ctrl+Enter is used for complex inputs such as combo dialogs.
CRM-1870
Addressed a potential vulnerability where a request involving integer values outside of the valid range caused an incorrect HTTP response code (HTTP 500) to be returned.
CRM-2468
To avoid unnecessary complication, the unused inform:DB and insights:Insights data sources have been removed. All tables in those data sources can now be manually removed, and if they are implemented as their own databases, the tables can be dropped.
Also, the Interest custom field type originally added for supporting Insights has not been removed, but it no longer drives any OOB functionality.
CRM-2674
Previously, the association filter was sometimes still applied when a user cancelled configuring dashboard filters. This issue has been resolved.
CRM-2741
Previously, drilling down in charts showed incorrect results based on the records mentioned in COUNT. This issue has been resolved.
CRM-2993
Previously, when an activity plan was removed from an opportunity, the activities added as activity plan steps were not removed. This issue has been resolved by ensuring that step activities are removed when the activity plan is deleted.
CRM-3198
Previously, if a report included in a dashboard was updated, the related dashboard item did not always finish updating, leaving the dashboard in an incomplete state. This issue has been resolved.
CRM-3397
Previously, reducing the size of the application window while viewing the Reporting workspace could allow users to perform actions they did not have access to, creating potential security and usability issues. This issue has been resolved.
CRM-3469
Previously, scrolling through historical calendar items could cause an error making the UI unresponsive. This issue has been resolved by limiting the number of returned instances.
CRM-3537
Previously, applying certain filters and groupings to Custom Fields associations could result in an err.persistence.ungroupedHaving error under some circumstances, preventing report updates. This issue has been resolved by correcting the grouping and filtering logic.
CRM-3560
Previously, when a user tried to create a merge field that matched the value in the custom token field of another merge field, the resulting error message did not help to identify the conflicting field. This issue has been addressed by providing more detail in the error message.
CRM-3760
Previously, exceptions thrown during report export did not automatically flag the export as failed, leaving users uncertain about the report export status. This issue has been resolved by automatically flagging failed exports.
CRM-3789
Previously, when viewing a dashboard while the report belonging to the dashboard was being edited, expanded subgrouping values in the report were displayed as “(Blank)”. This issue has been resolved by not showing subgroupings while a report is being edited.
CRM-3811
Previously, when a task or schedule item was updated by modifying both activity participants and another field at the same time, the Updated Activities tab didn’t always display the updated information. This issue has been resolved.
CRM-3858
Previously, exporting a report with collection attributes to Details (Excel) in “Collapse into a single row using a delimiter" export mode would not complete, leaving the export in progress indefinitely. This issue has been resolved.
CRM-3859
Previously, while exporting a report to Detail (Excel), if the user attempted to perform another export, the Summary (Excel) menu item was disabled. This issue has been resolved and the Details (Excel) menu item is disabled during the export instead.
CRM-3900
Previously, the application allowed invalid filter expressions to be saved, causing errors during startup. This issue has been resolved by improving filter handling.
CRM-3939
Previously, recurrence expansion performance was hampered by the sort function, leading to slow processing of recurring events. This issue has been resolved.
CRM-3951
Previously, a failure in the RecurrenceBatchJob could result in an SQLConnection leak, potentially impacting database resource management and system stability. This issue has been resolved by ensuring that SQL connections are properly released even when the batch job encounters errors.
CRM-3989
The following HTTP headers were missing from the EWS GetStreamingEvents requests: X-AnchorMailbox, client-request-id, return-client-request-id. This was fixed.
CRM-4015
Previously, the host header validation feature only logged rejected hosts at DEBUG level, making it difficult to troubleshoot push connection issues. This issue has been resolved by logging the first occurrence of each rejected host and missing host headers at the WARN log severity level.
CRM-4045
Previously, users performing an export on the Opportunities workspace received an error if an exported column contained a unitBind with a specified value. This issue has been resolved.
CRM-4052
Any nested menus that do not have any valid values (for example, the Add menu when adding a business process to a contact in a deployment without active business processes) now clearly show the “No data to display” message.
CRM-4069
Prior to this release, the data tables on the Reporting workspace did not always consistently display the buttons for available actions for each row. This issue has been resolved and the same buttons are always displayed for each type of item. Different actions are available for template reports, non-template reports, template dashboards, and non-template dashboards.
CRM-4139
Previously, when an environment running on a PostgreSQL database used the RIGHT calculated field function in reporting, an unexpected error was thrown. This issue has been resolved by casting the second argument of string-right API to generate a compatible SQL code.
CRM-4151
Previously, drilling down in the Visualization tab of a report would show nothing unless a count was specified, making it difficult to analyze grouped data. This issue has been resolved by updating the drill-down logic to display results even when count is not specified.
CRM-4177
Previously, removing the text from the Name field in a blank report and then attempting to save the report would cause the report to hang, with no validation triggered and the Save button disabled. This issue has been resolved by ensuring that name validation is properly triggered and the user is notified that the Name field is mandatory.
CRM-4179
Previously, users encountered an error when attempting to sort the data table on the Export History tab for a report by the “File name" column, which prevented them from reviewing and organizing export records. This issue has been resolved.
CRM-5380
Previously, certain URLs referencing static resources (for example, /images, /fonts, /icons) on folder mixins could expose directory listings when accessed externally. This issue has been resolved by updating the server handling logic to mask directory contents and ensure consistent error messaging, preventing unintended exposure of file names.
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.
This issue is currently only applicable to NexJ CRM deployments in Cloud environments.
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.
This issue is currently only applicable to NexJ CRM deployments in Cloud environments.
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.