Connector Release Notes

Connector Release Notes

Business 360 FEP Connector

Business 360 FEP Connector

Fixed issues

Issue
Description
MDMN-87983
If you run the Secure Agent through a proxy server, the Business 360 FEP Connection might fail.
(December 2022)
MDMN-63373
When you run a mapping with multiple target objects that belong to the same business entity, the mapping runs successfully, but you get incorrect metrics on the job details page. The number of rows processed does not display separately for each target object as expected.
(November 2022)
MDMN-83586
When you create a mapping with a Business 360 FEP connection to write data to the Business 360 data store and select a field group as the target object, the
Target Fields
tab might incorrectly display the root fields instead of the selected field group fields. This could be because of the change in display name of the corresponding business entity in Business 360 Console.
Workaround: To view the target field group fields on the
Target Fields
tab, ensure that you update the changed display name of the corresponding business entity to its original name in Business 360 Console.
(September 2022)
MDMN-81890
When you create a taskflow with multiple mappings with the Business 360 FEP connection to ingress large number of records, the time taken for each mapping to process data increases when compared to the previous mapping in the taskflow.
(September 2022)
MDMN-71914
Mappings that you create using the Business 360 FEP connection might fail intermittently with the following error:
[FATAL] java.net.MalformedURLException: no protocol: null/cert-service
(December 2022)
MDMN-67648
When you run a mapping with a source object that contains a large number of records and with a relationship as the target object, the Business 360 FEP Connector processes only few hundred records correctly. The format of the remaining records is incorrect in the target.
(February 2022)
MDMN-66921
In a target transformation, if you specify business entity fields as the target object, you can map the
businessId
field on the
Field Mapping
tab. However, the Business 360 FEP connector does not process the value of the
businessId
field when you run the mapping.
(February 2022)
MDMN-66355
In a target transformation, if you map an input field to a target field with the field name exceeding the permissible limit of 75 characters, the truncated name appears on the
Field Name
column in the
Target Fields
section of the
Field Mapping
tab. The mapping fails with the following error:
Not all input columns presented in target
(August 2022)
MDMN-63869
The Business 360 FEP Connector does not support source transformations. If you use a Business 360 FEP connection in a source transformation, the mapping does not process any records and the status of the mapping incorrectly displays as
Success
.
(February 2022)
MDMN-63511
When you run a mapping with a predefined relationship as the target object, if you do not map the business entity field on the
Field Mapping
tab, the Business 360 FEP connector does not update the business entity field in the target data.
(May 2022)

Known issues

The following table describes known issues:
Issue
Description
MDMN-121918
When you run mappings that use a Business 360 FEP connection, the mappings might fail intermittently with the following error:
java.net.MalformedURLException: no protocol: null/metadata
Workaround: To resolve this issue, see the Error: java.net.MalformedURLException Knowledge Base article.
(April 2024)
MDMN-128369
MDMN-120462
When you map the source fields that contain boolean values, such as true and false, to the target fields, the Business 360 FEP connector incorrectly processes both values as false. The Business 360 FEP connector processes them incorrectly because it identifies only 1 and 0 as boolean values.
(October 2023)
MDMN-112677
When you run a mapping task that uses a Business 360 FEP 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-112219
When you use a Business 360 FEP connection to ingress a large number of records, the processing time is significantly high.
(July 2023)
MDMN-110788
If a single mapping contains a hierarchy and relationships within the hierarchy as target objects, the mapping runs successfully but doesn't write any data to the target objects.
(July 2023)
MDMN-110787
In a target transformation, if you specify relationships as multiple target objects, the mapping runs successfully for the first target object but fails for the rest.
(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-96083
When you map multiple targets to multiple target objects using a Business 360 FEP connector that uses a proxy-enabled Secure Agent, the mapping runs successfully even though the data doesn't get written to any of the target objects.
Workaround. Disable the proxy server for the Secure Agent.
(February 2022)
MDMN-65803
When you specify a relationship as the target object in a mapping, the connector catalog displays only the GUID values of the relationships instead of the display names. When you export these mappings, the GUID values change and prevent you from reusing the mapping.
Workaround: After importing the mapping, manually specify the required relationship with the changed GUID value in the connector catalog and select
Retain field Mapping
check box. On the
Field Mapping
tab, choose
Previous Mapping
in the
Automap
list and run the mapping.
(January 2022)
MDMN-65782
In a target transformation, if you specify a hierarchy and one or more relationships within the hierarchy as multiple target objects in a single mapping, the mapping fails.
(January 2022)
MDMN-65279
A mapping does not reject the records that do not contain a value for the sourcePKey field.
(January 2022)
MDMN-60298
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.
(January 2022)

0 COMMENTS

We’d like to hear from you!