[CMDB-IRE] When we move the non-existing columns to the reconciliation engine (using updates sets) the reconciliation does not work properlyIssue When we move the update set with the invalid columns (columns that do not exist) to the target instance then the reconciliation rules fail OR showing the incorrect number of attributes on the CI Class Manager' Reconciliation rules. Steps to Reproduce: Source Instance:1.1. Using the Default update set, create some columns on any table (Ex: cmdb_ci_pc_hardware)1.2 Now, create some update set and use this update set.1.3 Open the CI Class Manager and select the table cmdb_ci_pc_hardware.1.4. Goto Reconciliation Definitions, and add a new reconciliation rule with all the attributes (so the custom fields also added).1.5. Now, complete the update set and export the XML.OR simply use the attached remote update set that I used.Note: Observe that the update set only have the new reconciliation definition related updates but not the new columns we created.Target Instance:2.1. Login to the instance and goto CI Class Manager.2.2. Open the table/class cmdb_ci_pc_hardware and goto Reconciliation Definition. Note the number of attributes under this table.2.3. Now, goto retrieved update sets.(( Application Navigator >> Retrieved Updates Sets))2.4. Right-click on the list header and select the option "Import XML".2.5. Now, select the earlier created XML (simply use the attached XML) and Preview the Update set and commit.2.6. Now, repeat the steps 2.1 to 2.2.2.7. You will see the number of attributes is incorrect and it still considers the invalid/non-existing columns.2.8. Even if we try to do cache flush it still exists.CauseThe issue is because there are invalid/orphan/non-existing columns exists and that leading to failure of the engine to identify.ResolutionThe only workaround is to open the reconciliation rule and save it again.