Connector Release Notes

Connector Release Notes

Business 360 Connector

Business 360 Connector

Fixed issues

The following table describes fixed issues:
Issue
Description
MDMN-54343
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:
Operation request cannot be empty
(April 2023)
MDMN-87983
If you run the Secure Agent through a proxy server, the Business 360 Connection might fail.
(December 2022)
MDMN-71914
Mappings that you create using the Business 360 connection might fail intermittently with the following error:
[FATAL] java.net.MalformedURLException: no protocol: null/cert-service
(December 2022)
MDMN-58950
In a target transformation, if you specify two different hierarchies as the target objects, the mapping successfully processes data for one of the target hierarchies and results in errors for the other target hierarchy.
(December 2022)
MDMN-67449
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.
(February 2022)
MDMN-58096
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""}"
Workaround: Run the mapping again after some time.
(May 2022)
MDMN-58062
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.
(February 2022)
MDMN-56094
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:
java.lang.RuntimeException: [SDK_APP_COM_20000] error [error [Failed to validate the data object because the entry [Organization to Organization] already exists in the collection [null]. Provide a unique name for the entry.]]
Workaround: Specify unique display names for the assets in your business application and create the mapping.
(September 2021)
MDMN-55534
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:
com.informatica.adapter.sdkadapter.projection.semantic.manual.SD_PlatformField cannot be cast to com.informatica.adapter.sdkadapter.projection.semantic.auto.SAD_ComplexField
(October 2021)
MDMN-55136
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.
(October 2021)
MDMN-50436
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.
(October 2021)
MDMN-48388
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.
(July 2021)
MDMN-47882
When you create a taskflow to run multiple mapping tasks in parallel, loss of data might occur.
(July 2021)
MDMN-47851
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:
com.informatica.adapter.sdkadapter.projection.semantic.manual.SD_PlatformField cannot be cast to com.informatica.adapter.sdkadapter.projection.semantic.auto.SAD_ComplexField
(October 2021)
MDMN-46041
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.
(July 2021)
MDMN-43456
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.
Workaround: To increase the Java heap size, run the mapping after you configure the following JVM options in the Secure Agent properties:
  • JVMOption1=-Xms32m
  • JVMOption2=-Xmx1024m
(March 2021)
MDMN-42121
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.
(March 2021)
MDMN-41962
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.
(August 2021)
MDMN-41758
When you select a hierarchy relationship as the target object in a mapping, the mapping fails.
(May 2022)
MDMN-40445
The log files include more detailed debug information that results in increased file size.
(February 2021)
MDMN-38928
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:
[FATAL] *MongoException while trying to establish connection Unable to look up TXT record for host mdmnext-qa-mrel1-blue.0o9pv.mongodb.net
(April 2021)
MDMN-37250
You cannot modify the targets in the mapped output groups. (September 2021)

Known issues

The following table describes known issues:
Issue
Description
MDMN-105037
After you import reference data sets with crosswalk mappings, import Cloud Data Integration mappings to import reference data sets. After you import them, the Business 360 Connector fails to retain the source and target field mapping of the crosswalk mappings. When you validate the source and target field mappings, the following error message appears:
One or more mapped fields are no longer present in target.
Workaround: Select the crosswalk as the source or target object in the crosswalk mappings and manually map the source and target fields.
(October 2023)
MDMN-112677
When you run a mapping task that uses a Business 360 connection, the mapping task runs successfully but incorrectly displays the connection details from the log file as error messages.
Workaround: Ignore the error messages.
(July 2023)
MDMN-97751
In a target transformation, if you map the sourcePkey field that contains special characters to the target field, the target transformation fails.
Workaround: Use only the following special characters in the sourcePkey field:
.~!/'={}|:@#$^&*()-_+,<>?`
(March 2023)
MDMN-68378
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.
Workaround: Use individual source object for each field group in the mapping and associate the mapping in the taskflow to ingress data.
(February 2020)
MDMN-61616
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.
(November 2021)
MDMN-57313
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.
(September 2021)
MDMN-57029
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.
(September 2021)
MDMN-56747
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.
Workaround: Ensure that the sourcePKey field values don't exceed 300 characters.
(September 2021)
MDMN-55611
The log files do not include details of records that are rejected due to filter transformations. (August 2021)
MDMN-55439
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.
(August 2021)
MDMN-54198
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.
(August 2021)
MDMN-43676
If you do not include the following third-party website as an exception in the firewall of your organization, the mapping fails:
(February 2021)
MDMN-42263
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.
(February 2021)
MDMN-41967
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.
(January 2021)

0 COMMENTS

We’d like to hear from you!