NexJ Logo

Resolved issues for Data Bridge 3.4.3, 3.4.1, and 3.4.0

Version 3.4.3


An issue that meant that multiple manifest files were generated when zero records were exported as part of a view snapshot has been resolved.


Previously, the status for a snapshot process that was cancelled by a user could get stuck in the "Cancelling" state for an abnormally long time before converting to "Completed with errors." This issue has been resolved.


Previously, in isolated scenarios, missing error handling logic caused the query timeout errors to be reported in the Data Bridge log but not in the UI. This issue has been resolved.


Previously failed snapshots for views caused "delta" exports to incorrectly compute their set of records. This issue has been resolved.

Version 3.4.1


Previously, when you published a File (JSON) snapshot for a view in Data Bridge, selected the History tab, and the Snapshot subtab, the Date column in the data table displayed a timestamp that used the Coordinated Universal Time (UTC) standard instead of displaying the local time. This issue has been resolved.


An issue that meant that some currency characters were serialized as \uXXXX in the JSON output for views has been resolved.


Previously, and in some isolated cases, it was possible for Data Bridge to send an "update" streaming event to Apache Kafka when in fact a "delete" event occurred in NexJ CRM. This issue has been resolved.


Previously, it was not possible to include soft-deleted CRM records as part of snapshot output. This applied to both full and "delta" snapshots. A new feature has been added to address this issue.


Previously, if the Data Bridge server ran out of disk space while a delimited or a JSON file snapshot export was in progress, the process did not fail gracefully. A " No space left on device" error was repeatedly displayed in the UI, and the process would get stuck in the "in progress with errors" state. This issue has been resolved.


Previously, a single-threaded export of an Activity view with a date filter could perform poorly and eventually fail with the following error message: "Unable to retrieve data from CRM server. SQL error. (err.persistence.sql) (err.Bridge.CRMFeed.fetchError)". This issue has been resolved.


Previously, for Data Bridge views that queried large volumes of records from NexJ CRM, it was possible that the "Refresh Count" function found in the Preview tab in the UI could fail to display the updated object count if the request took longer than one minute to complete. The actual count was eventually updated successfully, however the UI failed to refresh. This issue has been resolved.


The "end time" of the previously executed snapshot for a view was used to determine the set of NexJ CRM records that changed and needed to be included in the output of a "delta" snapshot. In isolated scenarios, this incorrectly led to some NexJ CRM updates being excluded from the subsequent "delta" snapshot. The "start time" value is now being used instead.

Version 3.4.0


In some cases, when you included an associated object as part of the view definition, updates made to primitive attributes for that associated object, even if they are not included in the view, caused the view to publish the update. This issue has been resolved.


Previously, when you added an Act Series attribute to a Deals or Opportunities view and exported it to CSV, "Related Activities" displayed in the header of the exported file but no related activities data was exported. This issue has been resolved.


Previously, the values that were displayed in the Monitoring Dashboard for the Failed Export Count - Snapshot - Kafka statistics could be slightly higher (+1 for each page of processed data) than the actual number of failed messages. This issue has been resolved.


Previously, the set of attributes was not filtered correctly when you switched between the Basic and Advanced tabs when searching for fields on the Create View page. This issue has been resolved.


Previously, updates made to some associated attributes (for example, Address for a Contact) triggered Data Bridge to stream the update to Kafka even if the attribute was not selected as part of the data view. This issue has been resolved.


Previously, in an extremely unlikely scenario, an empty message was sent to Kafka if a Data Bridge view configuration was updated from JSON to the Avro format and a CRM data change event was triggered at the same time. This issue has been resolved.


Previously, the statistics in the Monitoring Dashboard did not match the export details provided in the Snapshot subtab in the History tab on the View Details page for views with numerous records in multi-node environments. This issue has been resolved.


Previously, it was possible to trigger multiple parallel snapshot export processes, which could result in the export status of a view to be reported as "In Progress" indefinitely. This issue has been resolved.


An issue that caused the status of a snapshot export process to only be updated after a significant delay has been resolved.


Previously, when you exported views to CSV format that contain nested associations, duplicate columns displayed in the CSV file, and they also included underscore characters. This issue has been resolved.


An issue that caused Unicode characters to not be exported correctly in CSV files has been resolved.


Previously, when you created a new Telcoms view, enabled streaming for it, and created a new Telcom for a contact in NexJ CRM, all Telcom data belonging to this contact was sent to Kafka, and not just the new Telcom "create" event as expected. This issue has been resolved.


An issue that meant that exported date values were incorrectly adjusted backwards by 1 day has been resolved.


An issue that meant that commas were displayed for integer values in exported CSV files has been resolved.


An issue that meant that you were unable to create users in NexJ Admin Console when their login names were longer than 10 characters has been resolved.


As issue that meant that when you added filter criteria that contained double quotes Data Bridge triggered an unexpected error has been resolved.


An issue that meant that metadata import errors were unreadable as the dialog was not resizable has been resolved.


NexJ CRM integration errors that are formatted as strings are no longer hidden.


Previously when you clicked Add View in the View Explorer in Data Bridge, clicked Select in the Import View Definition from JSON field, selected an invalid JSON view (for example with a missing subject area), and clicked Open, no message was generated in the Data Bridge UI to warn you that the view was not imported because it was invalid. This issue has been resolved.


Previously, updates to primitive attributes of an association object that were not selected as the view attributes would cause Data Bridge to publish steaming updates. For example, when you created a new Contacts view, selected the Full Name and Telcoms attributes, enabled streaming, saved the view, and modified any Telcom in NexJ CRM (for example, updated a business phone number for a contact), the expected results were that no streaming updates would be published. Instead, an update event occurred that caused the view to publish unnecessarily. This issue has been resolved.


Previously, specifying any UTF-8 characters as part of the filter criteria in a view, caused Data Bridge to apply an incorrect filter to CRM data. For example, a meeting in CRM titled "Réunion de révision annuelle" could not be selected with the "starts with" operator, and "Réunion" as the filter text value. No data would be exported. This issue has been resolved.


Previously, when you configured a value for the Kafka Namespace parameter in the Publishing Options tab for a view, you could not set its value to blank anymore. This issue has been resolved.