cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Issue with Fixed value mapping

0 Likes
2,007

Dear Experts,

I am stuck in a mapping situation as explained below and need  your help for resolution.

Mapping in contention  is as shown below :

As per this mapping the Substring should throw 3 character word and  in fix value mapping it is getting displayed correctly. The fix value mapping is as shown below:

queue result of Substring function in mapping :

Queue Result for Fix Value mapping :

Till this point every thing looks fine but when I clicked on the Queue of the Target field it throws out the error as:

Here it clearly shows that output of the key in fix value mapping is null, which contradicts the result of  fix value mapping queue.

Please let me know if any one else has faced this  issue before  or if you have any idea for the resolution of this issue.

Thanks and Regards,

Sudhir Kumar

View Entire Topic
baskar_gopalakrishnan2
Active Contributor
0 Likes

Just Few cents...  This is mere data discrepancy issue. I would recommend to sync/update the fix value  records always.  This problem could populate always with different values that comes from sender side... You might get a different string in the future like this. Go with atleast default value to take care this issue.