[LS-983] Mismatch in MW Inventory Update Date Created: 03/Mar/26  Updated: 08/Apr/26  Due: 04/Mar/26  Resolved: 07/Apr/26

Status: Closed
Project: L3 Support
Component/s: NEP
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Priyasha Tiwari Assignee: Srishti Kashyap
Resolution: Fixed Votes: 0
Labels: nep_dev
Remaining Estimate: 0 minutes
Time Spent: 1 week, 1 hour
Original Estimate: Not Specified

Attachments: PNG File MW IDU UPDATE DATE ISSUE.png     PNG File Screenshot 2026-04-03 144539.png     PNG File UPDATE DATE INCORRECT NEPIDU REPORT .png     PNG File image.png    
Customer:
Airtel India
Planned Start:
Planned End:
Defect Category: Implementation
Actual Start:
Date of Baselining:

 Description   

update date is not changing and showing the latest update for the IDU nodes and link data ..



 Comments   
Comment by Priyasha Tiwari [ 05/Mar/26 ]

sample node DLMW327_DL , circle Delhi

Comment by Srishti Kashyap [ 20/Mar/26 ]

Build 3.7.71.567 is released for the issue.

Comment by Abir Messaikeh [ 25/Mar/26 ]

After patch applied still the update date for this node are not changing , please check the error Screenshot from .177 test where the import was done after the patch was applied ..

Comment by Anonymous [ 03/Apr/26 ]

Hi Dear
As checked on test server the IDU nodes are updating correctly and showing correct data on the version DL_date created at .45 shared in trailing mail on importing xml shared. Attaching ss for same.

Comment by Abir Messaikeh [ 03/Apr/26 ]

we might proceed on PROD and check on PROD DL the result accordingly

Comment by Priyasha Tiwari [ 07/Apr/26 ]

DL PROD correct update is showing, need detail regarding this fix .

Comment by Anonymous [ 07/Apr/26 ]

The issue was caused because a case-sensitive comparison falsely detected a model type change (AMM2PB vs AMM2pB coming from xml). This triggered a validation that blocks modifications when transmission links are already connected, resulting in an exception thrown hence node not updating. Using equalsIgnoreCase resolved the issue by ensuring case-insensitive matching and preventing incorrect validation failure.

Comment by Priyasha Tiwari [ 07/Apr/26 ]

close

Generated at Fri Apr 17 11:55:44 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.