AROutput Step Treats NULL Differently with AROutput when Updating Records

 

Legacy ID:KA406422
Refer to the 'Duplicates' tab in Ar Output. The option used for 'Duplicate Request Action' is 'Update old record with new Record's data'
With this option when SetField API is call, field value is not modified/updated in case if it is blank/empty.
So here even if the constant is defined with null/empty value , SetField API ignores it with 'update'option specified and so the old value is retained.

Instead if you chose option 'Replace New record with Old record' for 'Duplicate Request Action'.
Then SetField API replaces old record and here empty/null value is not ignored.
So with this 'Replace' option when you run transformation, Last Name field will be made blank with the current use case.

In case if you wish to use 'Update old record with new Record's data' option.
Then you will have to modify constant and use keyword $ NULL $ in value field , which is euqivalent to empty value but SetField API understands it as allowed value and doesn't ignore it.
Now when you run transformation with 'Update old record with New record data' option Last Name field will be made blank.

So there are 2 options available here -
1) Modify AROutput and Update 'Duplicate Request Action' to 'Replace New record with Old Record' in Duplicate tab.
2) Modify added constant and set in the value column instead of blank.


Testing confirms 'Replace New record with Old Records data' to update. Use of Constant, option #2 takes the constant as literal text string.

Defect SW00461763 created to address Constant/string issue.

This is a known issue and requires bigger change - Implementing Keyword support in UDM.Only option left to handle 'No value' is to implement keyword support which will handle $ NULL $ and this needs to be implemented as a RFE/ Feature. We will not be able to deliver it as a hot fix.