The following are a list of the most critical known issues in the current release of NexJ Data Bridge and problem workarounds, where possible.
When the object count is refreshed in the Preview tab for a Data Bridge view that contains associated objects (for example, Addresses for a Company), and the Changes (primary or associated fields) option is selected in the Publishing Options tab, the displayed count may be higher than the actual number of objects that would be published. This defect only affects the preview functionality and not the accuracy of data being published.
When the NexJ CRM Data Bridge Adapter is installed in an environment with Kerberos authentication enabled, the default system user ID, "brgadmin," is not seeded in with the correct domain suffix appended to it. The login name needs to be manually renamed.
After you create a view with filters and save it, the filter captions in the About tab on the View Details page may not match the filter captions originally provided on the Create View page in the Data Selection tab, and in the Filters section.
When you create a new Contacts view, add the
Full Name and
Related Opportunities attributes, enable streaming, save the view, and then create a new opportunity or delete one in NexJ CRM, instead of publishing a single update message for the related contact to Kafka, Data Bridge produces two update messages (one for the related contact and one for the related user).
A possible workaround is to add a filter "Type equals Contact" to such a view.