Audit Data inconsistency in Asset recordsSummaryData inconsistency in Asset records. Few fields were getting updated by an Assignee again even though its filled already. -Assigned to name-State-Substate ReleaseTokyoInstructionsSteps to reproduce: 1. Navigate to alm_hardware record.2. Check History-> list and filter by "Assigned To" / other fields3. Check that there will be 2 records with the same Old and New values. Cause: 1. Reason behind the issue is the following BR is which putting the assigned_to field back to empty valueClear Assigned To on updatehttps://<instance-name>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=594e2e93ef02200035c61ab995c0fb59Reset Assigned Tohttps://<instance-name>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=81954b03c30331004e44dccdf3d3ae72 These BRs are based on asset state. 'assigned_to' field is cleared if the state is On Order, In Stock, In Transit. At these states, asset may not have an owner. 2. Also due to import XML. Updates made by an XML import are not audited. There is a sys_mod_count field on the alm_asset record, which is where "Update Count" in sys_audit comes from. It can not be same for all the records.