Last_Discovered value got updated without having field mapping from data source

[jomonmathew]

Recently we have integrated with 1E tackyon for CMDB discovery. We are mapping only some limited fields to cmdb for the discovery. We don't have last_discovered(most recent discovery) field mapping in transform map field mappings. But after reconciliation using the transform scripts in the import , last_discovered field is getting populated. How can we prevent this

[msd93]

Hi @jomonmathew 

To prevent this behavior, try the following steps:

1. Review Transform Script Logic:

   • First, review the transform script logic associated with the reconciliation. Look for any code that explicitly updates the Last_Discovered field. The script may contain logic that assigns a value to this field during the reconciliation process.

2. Modify Transform Script:

   • If you find that the transform script is updating the Last_Discovered field, modify the script to exclude this field from updates. Remove any lines of code that set or modify the Last_Discovered field in the transform script.

3. Use a Condition:

   • If there are specific conditions under which you want to update the Last_Discovered field during reconciliation, add conditional statements to the transform script. Ensure that the field is only updated when the desired conditions are met.

4. Field Mapping Configuration:

   • Check the field mapping configuration for the reconciliation process. Verify that the Last_Discovered field is not mapped to any source field in the field mapping settings. If it is mapped, remove the mapping.

5. Debugging and Testing:

   • Debug the transform script to understand its behavior during reconciliation. You can use logging statements or debugging tools within the script to trace how and why the Last_Discovered field is being updated. Testing in a development or testing environment can help you identify the specific code causing the issue.

6. Review Reconciliation Rules:

   • Review the reconciliation rules associated with the import set. Ensure that the rules are correctly configured and that they do not contain any actions that update the Last_Discovered field.
   •  

7. Monitor and Audit:

   • Implement monitoring and auditing mechanisms to keep track of field updates during reconciliation. Regularly review reconciliation logs and reports to ensure that the Last_Discovered field is not being updated when it shouldn't be.

Hope this helps you.