Inconsistent Behavior of Data Certification Filters Across Instances After DeploymentIssue Why does cert_filter record sys id changes whenever we make any changes and save the record? When deploying modified Data Certification filters to another instance, the old filter is not getting inactivated as expected, leading to duplication and inconsistent filter states across environments. SymptomsSteps to reproduce:1. Navigate to Data Certification filters in any instance (Instance 1)https://<instance>.service-now.com/now/nav/ui/classic/params/target/cert_filter_list.do 2.Open any existing record or create new record and notice the sys id- After navigating to the Data Certification filters page, verify the sys_id of the newly created record. 3. Export the xml of the record and move to another instance (Instance 2) 4. Observe the Issue in Instance 1 and Instance 2:- Now go back to instance 1 record and make any changes to the record, you will notice that the sys_ids for these filters are different in both environments now.- This difference in sys_id has caused duplication after modifications were made, resulting in inconsistencies between the environments.ReleaseAll releases CauseThis is expected behaviour by designResolutionThe legacy data certification supported different versioning of Certification filters, and it was by design at that time. We are deprecating legacy Data certification, in favor of the new Data certification experience in CMDB Workspace.https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/configuration-management/concept/data-cert-exp-cmdb-workspace.htmlIf customers need the certification conditions in a data certification schedule (in the new experience, it would be called a "policy), then we would advise for customers to leverage the new Data Certification experience in CMDB Workspace, available with CMDB Workspace v6+ You can create Data certification policies in the new CMDB Workspace experience, using this feature called "Data Manager" to create certification policies and ship the policy records across different workspaces. The sysIDs of the data manager policies will not change.https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/configuration-management/task/data-manager-create-policy-wrkspc.html Note: The legacy Data certification is planned for deprecation in Z release.