Data Integration Connector Release Notes > Connector and connectivity issues > Business 360 FEP Connector
  

Business 360 FEP Connector

Fixed 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.
(May 2024)
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.
(November 2023)
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.
(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.
(August 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.
(August 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.
(August 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-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: .~!/'={}|:@#$^&*()-_+,<>?`
(July 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.
(July 2023)
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.
(July 2023)

Known issues

The following table describes known issues:
Issue
Description
MDMN-153393
When you configure multiple partitions in a Source transformation to export a large number of records, the mapping task uses only a single partition to process data during the extract step.
(October 2024)
MDMN-144495
When you export hierarchies and relationships by using Business 360 FEP Connector, the egress job might fail at the stage step with the following error:
Invalid JSON input: Unexpected character
(July 2024)
MDMN-144372
When you export source records that contain validation errors, the exported data doesn't include the source systems of the field groups. The issue occurs only when the preview feature for validation errors is enabled in your organization.
(July 2024)
MDMN-123482
When you export hierarchies and relationships that belong to a specific source system by using Business FEP Connector, the egress job exports hierarchies and relationships from all the source systems.
(November 2023)
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-65279
A mapping does not reject the records that do not contain a value for the sourcePKey field.
(January 2022)