Data Mapping

Owned by Deepak Kumar (Deactivated)
Last updated: Aug 22, 2024 by Rajeev Rai
3 min read

Issue

Cause

Diagnosis

Resolution

Any special character like single quote or $ or other special characters is present inside the value part of the value map which causes issue while using in mapper.

Check the Value Maps/Input file and see if there's any special character like single quote or $ or other special characters in the values you have provided in the value map/Input file .

  1. After trying to access the XSL tab of a Data Mapping, it responds XSL is invalid.

  2. Check diagnostic from Adeptia dashbord and see Invalid byte related error.

Remove the special characters and save the value map/Input File.
Map Value need to add in Cdata and check if the issue is resolved.

A sequence of more than one item is not allowed in date format function.

This issue typically arises when the Date Format function is used in a mapping rule where a for-each loop should be applied to the parent node but is not. As a result, multiple date values are passed to the Date Format function instead of a single date value, leading to the error message "A sequence of more than one item is not allowed...".

Search the Mapping XSL: Locate where the Date Format function (process DateFormat) is being used in the Mapping XSL.
Identify Incoming Values: Determine the incoming value(s) of the source data, such as "20170222...", "3", etc.
Map to Target Field: Figure out the target field that this data is mapped to according to your business requirements.
Check for For-Each Loop: Ensure that a for-each loop is applied to the parent node if multiple date values are expected.

To debug the issue, the quickest way would be to search the Mapping XSL for where the Date Format function is being used (i.e. process DateFormat from the error message).
Next, you can identify the incoming value(s) of the source data ("20170222...", "3", ...) then figure out what target field that data is mapped to per your business requirements.

Value Map referenced value/key cannot be directly used in if else statements

Value map inside an if-else statement without defining it in a variable first will result in an error.

When examining the if-else statement, ensure that the value map is defined in a variable before being referenced.

To resolve this issue, define the value map in a variable before using it in the if-else statement in the mapping expression.

Performance Issues: Slow data processing or response times in debugger or slow processing of mapping.

  1. Resource limitations (CPU, memory, disk space).

  2. Large data volumes.

  3. Inefficient data mapping.

  1. Monitor the performance metrics of the server (CPU, memory usage, disk I/O).

  2. Analyze data volumes being processed to identify potential bottlenecks.

  3. Review the data mapping and transformation processes for inefficiencies.

  1. Optimize data mapping and transformation processes: Simplify the steps involved to minimize unnecessary processing time.

  2. Allocate sufficient resources: Ensure that the Adeptia Connect server has adequate CPU, memory, and disk space to handle the integration workload.

  3. Implement caching mechanisms: Use caching to store frequently accessed data temporarily, reducing the need to repeatedly process the same data.

Connectivity Problems: Difficulty connecting to various data sources(DB/API) or systems in the mapping.

Network configurations.
Firewall settings.
Authentication issues.

  1. Check network configurations to ensure proper routing and access.

  2. Inspect firewall rules to verify that necessary ports are open for communication.

  3. Validate the credentials used for authentication to ensure correctness and required permissions.

Verify network configurations: Ensure the network settings are correctly configured for the intended connections.
Check firewall rules: Confirm that the firewall is not blocking the necessary ports required for communication with data sources or systems.
Double-check authentication credentials: Ensure the credentials used are correct and have the necessary permissions to access the data sources or systems.

Mapper window Loading Issue

While Uploading the file in the Data Viewer, It get hanged and keep on loading

When a large EDI data file is uploaded into the Mapper Data Viewer, it takes an excessive amount of time to parse the EDI file.

The root cause is that the system internally parses the XSD multiple times. Specifically, the number of parses is equal to the message count present in the EDI file.

This repeated parsing leads to a time delay that exceeds the gateway timeout limit.

Work around as suggested from Product Team:
Increase the gateway timeout.

Data Mapping failed in Sunlife Production Environment due to below error
Sourced file: inline evaluation of: ``import java.io.InputStream; import java.io.PrintWriter; import java.io.StringWri . . . '' : Method Invocation TransactionExecutor.executeTransactionWithTransID : at Line: 53 : in file: inline evaluation of: ``import java.io.InputStream; import java.io.PrintWriter; import java.io.StringWri . . . '' : TransactionExecutor .executeTransactionWithTransID ( childCtxMap , errorHandlingFlowId , service .getSubject ( ) , true ) Target exception: com.adeptia.indigo.services.ServiceException: Error in running process flow with Process Flow ID: "010000001109167115826190800160": Entity of type com.adeptia.indigo.transaction.IndigoTransaction with [id, version]=010000001109167115826190800160 not found

 

 

Â