3042857 - Integration Center shows correct result in Preview but delivers wrong value in Output file (Run now)

In Integration Center, one or more fields show correct value in preview but delivers wrong value in the output file (Run now).

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

• SAP SuccessFactors HXM Suite
  
  • Integration Center
    

1. Create an Integration Center job.
2. Check the integration preview on "Configure Fields" tab - it shows the expected data.
3. Run the integration or wait for it to run on its schedule.
4. The data from the preview is not returning - unexpected data is returning instead.

1. Calculated fields
   1. The data type of a manually typed value should be null. You can confirm that by looking at the "Integration Definition" file (the ICD file), searching for the value you manually typed in the calculation.
      
      For example, here the value "1970-01-01T00:00:00Z" was manually typed:
      
      
      This is how it looks like in the ICD file, it has no "dataType" field assigned to it (which is fine):
      
      
      If we associate some field to it instead, like the createdDateTime:
      
      
      It will assign a dataType to the field in the ICD, which is also fine:
      
      
      But if we revert this field back to the manually typed value, that dataType remains in the ICD, causing the issue:
      
      
      
      
   2. If you have Calculated Fields with dates comparison, the issue happens when you are are not using a proper DateTime format while doing the calculation. For example: instead of 2020-09-01T00:00:00Z, you are using the format 09/01/2020 in the calculation:
      
      
      
2. One-to-Many navigation in the affected field.
3. Scheduled and Current versions of the Integration Center job are not matching.

For each Cause, we will present a resolution below: 

1. Calculated fields
   1. Data type associated with a manually typed field:
      To fix this issue you'll have to recreate the calculated field from scratch.
      
      
   2. Calculated fields with Date comparison:
      Make sure the Date fields being compared are in the same format. Note: in calculated fields, you cannot use custom dates for date comparison (different datatype comparison is not allowed in calculated fields). All the fields must be of the same datatype while performing a comparison. Currently there is no workaround for this: If you want to use DateTime as a data type of the calculated field, then you will have to ensure that all the fields are of DateTime data type.
      
      Note: The DateTime field comparison will work in preview even with value 09/01/2020 but will not work at the run time due to incorrect field type. Hence we need to change the value from 09/01/2020 to 2020-09-28T00:00:00Z.
      
     
2. Calculated fields or regular fields with One to Many navigations can also cause these kind of behaviors in the Output file. If you are using such navigations, only use them if you are following the example from KBA 2528579 - “Calculated field” is not calculating correctly for few data - SuccessFactors Integration Center.
   • More details about One-to-many behavior in Integration Center: 3087941 - One-to-many behavior in Integration Center
     
3. Please make sure to match both versions according to the below KBA:
   3126507 - Scheduled and Current versions not matching for Integration Center job

Integration Center Preview, Integration Center Output, Configure Fields, Calculation, Date Field, Date Format, One to Many, IC, Run NOW, DateTime, data type, calculated field, preview, calculated, Integration Center, , KBA , LOD-SF-INT-INC-FWK , Integration Center UI Framework , Problem