Data Integration Connectors
- Data Integration Connectors
- All Products
If you run the Secure Agent through a proxy server, the Business 360 FEP Connection might fail.
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 Fieldstab 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 Fieldstab, ensure that you update the changed display name of the corresponding business entity to its original name in Business 360 Console.
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.
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
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.
In a target transformation, if you specify business entity fields as the target object, you can map the
businessIdfield on the
Field Mappingtab. However, the Business 360 FEP connector does not process the value of the
businessIdfield when you run the mapping.
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 Namecolumn in the
Target Fieldssection of the
Field Mappingtab. The mapping fails with the following error:
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
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 Mappingtab, the Business 360 FEP connector does not update the business entity field in the target data.
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:
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.
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 Mappingcheck box. On the
Field Mappingtab, choose
Previous Mappingin the
Automaplist and run the mapping.
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.
A mapping does not reject the records that do not contain a value for the sourcePKey field.
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.
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.
Updated March 09, 2023