Tested Fine on Test platform,Patch deployement pending on prod , later will ask customer for the closure

General preview of work related to this issue:

• Financial records with serial numbers were stored in nep_history_reference table with status is_decomissioned false, even if the asset having the serial number no longer exists, we fixed this issue by changing the status of is_decomissioned to true for all financial records

• Changing Object id of a network element will lead to duplicates in history (one with old name, one with new name) same for physical configuration applied to this element, we fixed this issue in code, + cleanup scrip to clean records with old names

• if we have 2 network element of different types with same object id, physical configuration for both elements will have the same name in history we fixed this issue by adding an infix to physical configuration in history that specifies the type of network element (scripts + code) for example : "Cabinet_IDU_objecitd/c1_version"

• Clean data in unmapped report with cleanup scripts then add serial number to passive nodes + sync process to fix data

patch needed: 3.7.1.688 + upgrade directly to 3.7.1.689

Dear @Wajdi Jomaa,

As discussed over chat that there are still some unsolved duplicates which are not reported by customer but exist in the network.
Could you pl provide me the ETA ,as I need to share update on this ticket with customer.