what is the change date if parent NEs Core, RAN, etc ?

https://mobinets-my.sharepoint.com/:u:/g/personal/basant_kumar_nuiva_com/Eegc4u6qBWtNtY4GrT4WzbABLxsDdcnA4XtnfH2hQMRhjw?e=uwZRxv

https://mobinets-my.sharepoint.com/:u:/g/personal/basant_kumar_nuiva_com/EciuB4M0BK1AsaxhnmYaWJMBfKFhMsUvHMTiQcixor7hgg?e=F8yS2j

As you can see in the Screenshot the parent site LUK15I for the highlighted board is not present in NEP.

As checked the parent node of board is coreelement LUC-GMT-5GSM-MME-03 which is present in NEP also updatedon 22-02-2025,also the parent site LUK15I is also present in HP circle. Hence the board existing in NEP. During import over import process only creation and updation of Nodes and there respective sub elements. Also as the respective node is not present in xml hence there is no updation of related physical configuration. Attaching screen shot.

We found an issue in the JK circle. In the SRANBS report, the same node is appearing twice on is getting updated while the other is not. Due to this, the respective boards are also not getting updated, and board are appearing in the laTEST XML. If the node not present in the XML had been deleted, the new board elements would have been updated. so the "import over import" logic is not working correctly and needs to be checked.

refer the error snap

the sample case shared of JK no longer in NEP when checked. also @Priyasha as discussed please inform if the other node deletion needed to be included in api deletion for deletion.

Hi, A new sample case from the Punjab Circle has been shared. The gNodeB LUD240 is updating, and six cells are mapped under this node. However, only two cells are getting updated and are reflected in the XML data. The remaining four cells, although mapped to this node, are not updating and are also not getting parsed in the XML .

Ideally, these unmapped cells should be automatically deleted during the import-over-import process. Please review this sample node and share the Root Cause Analysis on top priority.

all the screenshot are attached.

new sample case attached for working, @khaled Khalil please check with L3 if not occupied in some priority 0 task then proceed to work on this .

HI Dear as explained During import over import process only creation and updation of Nodes and there respective sub elements. Also as the respective node is not present in xml hence there is no updation...it doesnt delete any data during import over import. If deletion is required please raise a CR jira for same.

How can we clean up the entries that are not getting imported into the XML, even though their parent nodes are updating? This cannot be done through API, as we need to remove these sub-elements...

@hassan please suggest, for new sample SS refer the latest date one

as discussed on call, refer to the screenshot attached for PB circle and check the configuration for cell report

Please provide a new sample case

HP-NLBDUN01-1 new sample from Hp circle , please check this sample on priority and same HP DB is connected to test .37

released build 3.7.71.546 with implementation of deletion of non updating cell of 2g,3g,4g,5g.

hi Srishti, we need detailed explanation on the implementation we did to rectify this bug please share

Hi Dear as explained implemention is regarding the deletion of cell and its sub-elements which are in NEP but not present in xml.

Hi dear Build 3.7.71.555 is released containing changes only a week older cells will be deleted if they are not coming in xml.

as discussed ,The release 555 was validating the insert date of cells for deletion, which is incorrect. Ideally, we should be referring to the update date of cells associated with active nodes. If these cells are not present in the XML for a week, they should be deleted. Additionally, the one-week condition should be configurable rather than hardcoded.

The release 555 was validating the insert date of cells for deletion, which is incorrect. Ideally, we should be referring to the update date of cells associated with active nodes. If these cells are not present in the XML for a week, they should be deleted. Additionally, the one-week condition should be configurable rather than hardcoded.

Hi,
Build 3.7.71.558 has been released with the changes mentioned in the trailing email.
The property npt.conf.cell.deletion.duration.days=7 has been added in the tr_configuration.properties file to support dynamic duration configuration.

hi as discussed this logic is not working as required for KK circle. where the connector huwaei import is done on alternate days and as we can see around 14k cells are deleting which are inactive and mainly of Huawei m2000 connector .

not ok

same as LS-918

Hi,
this must be closed as LS-918 is closed

Thanks