If you run the Secure Agent through a proxy server, the Business 360 Connection might fail.

If you specify a crosswalk as the source or target object in a mapping, the Business 360 Connector fails to load the metadata fields of the crosswalk on the

Field Mapping

tab.

When you run mappings using the Business 360 Connector, the mappings might fail intermittently with the following error:

Error occurred while accessing mongo atlas api - 
{""detail"":""The specified custom db role kTBrP3PDowhgwDO82h34ua-
hierarchyhierarchyhierarc-ing-egr-role-1629782459197 does not exist."",
""error"":404,""errorCode"":""ATLAS_CUSTOM_ROLE_NOT_FOUND"",
""parameters"":[""kTBrP3PDowhgwDO82h34ua-hierarchyhierarchyhierarc-ing-
egr--role-1629782459197""],""reason"":""Not Found""}"

In a target transformation, when you map a source field to a target field and if that source field is already mapped to multiple target fields, the scroll bar moves randomly and navigates automatically to a different position on the

Target Fields

section.

When you create a mapping, if the asset that you specify as the source or target object contains duplicate display names, you get the following error when you choose the asset type:

In a target transformation, if a field and an empty field group are within multiple nested field groups of a business entity, the mapping fails with the following error:

When you map two targets to two different business entities, the mapping runs successfully but writes all the data to one of the business entities and fails to write data to the other business entity.

On the

Field Mapping

tab, you cannot scroll the

Incoming Fields

and

Target Fields

sections separately for target transformations because the scroll bar is common for both sections.

In a target transformation that uses a single source object, if you map an incorrect input field to a target parentId field, the mapping results in an incorrect data hierarchy in the target system.

When you create a taskflow to run multiple mapping tasks in parallel, loss of data might occur.

In a target transformation, if you use a business entity that has a single-value field group nested between two multiple-value field groups, you get the following exception when you run the mapping:

When you map source fields that contain integers to the target fields, the Business 360 connector does not process values that contain comma as thousands separator.

When you run a mapping with source objects that contain a large number of records, the mapping fails with the following errors:

[ERROR] java.lang.OutOfMemoryError: Java heap space
SDKS_38201 There are not enough blocks to serve all reader groups, failing session.

When you map the source fields that contain boolean values as inputs to the target fields, the Business 360 Connector processes values

0

and

1

as false instead of false and true.

When you map input fields to target fields in a target transformation, the mandatory fields within nested field groups are not indicated with asterisk icon.

When you select a hierarchy relationship as the target object in a mapping, the mapping fails.

The log files include more detailed debug information that results in increased file size.

If the Secure Agent runs as a Windows service when the GlobalProtect virtual private network is enabled in your system, the mapping fails with the following error:

You cannot modify the targets in the mapped output groups. (September 2021)

In a target transformation, if you map the sourcePkey field that contains special characters to the target field, the target transformation fails.

Mappings that you create using the Business 360 connection might fail intermittently with the following error:

When you run a taskflow with a single source object to load more than 300,000 records into the Business 360 data store that contains more than 20 field groups, the taskflow fails.

In a target transformation, if the source object contains duplicate records with the same sourcePKey values, the Business 360 Connector doesn't process the duplicate records in the original order of the input data as expected. Instead, the connector processes the data in a random order that might result in incorrect processing of duplicate records in the target system.

In a target transformation, if you specify a hierarchy as the target object to which you want to write data, the required fields are not indicated with an asterisk in the

Target Fields

section on the

Field Mapping

tab.

When you specify an asset as the target or source object in a mapping, you retrieve the list of available assets by selecting the asset type and searching for the required asset using the search box. When you select a different asset type and delete the search text, the list of available assets doesn't appear.

In a target transformation, if the sourcePKey field value in the source object exceeds the permissible limit of 300 characters, the Business 360 Connector doesn't reject the records as expected. Instead, the connector incorrectly truncates these sourcePKey field values to 256 characters when you run the mapping. This behavior might result in multiple records with the same truncated sourcePKey values, and the mapping incorrectly considers these records as duplicates and rejects them.

The log files do not include details of records that are rejected due to filter transformations. (August 2021)

When you run a mapping, if large number of records are rejected, the log file size might be large. If you try to download the log file in the

My Jobs

page of the

Data Integration

service, the download fails. Workaround: You can view the log file from the Secure Agent.

In existing mappings for export jobs, if you edit the path for the source object to remove reference to

htype

and redo the mapping on the

Field Mapping

tab, the validation for the mapping fails with the following error:

In Business 360 Console, if you change the display name of a business entity that is used in a mapping, the

Field Mapping

tab fails to retrieve the mapping data.

If you do not include the following third-party website as an exception in the firewall of your organization, the mapping fails:

In the Business 360 Console, if you delete or update fields that are already mapped in the

Data Integration Mapping Designer

, the changes do not reflect in the mapping link of the source fields on the

Field Mapping

tab.

When you map input fields to target fields in a target transformation, if you map a field within a field group first and then map a root field from the same source, the mapping fails. Workaround: Delete all existing mappings and then map root fields first before mapping fields within field groups.