Details
-
Type:
Bug
-
Status:
Done
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Labels:
-
Customer:Zain KSA 3.X
Description
Click to add description
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
Dear @Bassem Sabbagh,
I have noticed that the Site ID is not parsing for NodeB (Nokia) in the XML, and the same issue is also present in NEP. It seems that the node name is not parsing, which is why it is not appearing, as it depends on the node name.
As I recall, I had shared a static sheet titled “RAN_Node Name_Matching” with #Juned to assist in parsing the node name for NodeB (Nokia).
@Sandya Sharma, could you please check and confirm whether the required static sheet (“RAN_Node Name_Matching”) is available in production before XML generation?
Thank you,
Indrasan
Show
Indrasan Yadav
added a comment - Dear @Bassem Sabbagh,
I have noticed that the Site ID is not parsing for NodeB (Nokia) in the XML, and the same issue is also present in NEP. It seems that the node name is not parsing, which is why it is not appearing, as it depends on the node name.
As I recall, I had shared a static sheet titled “RAN_Node Name_Matching” with #Juned to assist in parsing the node name for NodeB (Nokia).
@Sandya Sharma, could you please check and confirm whether the required static sheet (“RAN_Node Name_Matching”) is available in production before XML generation?
Thank you,
Indrasan
After confirmation with @Bassem/@Ahad manually full XML import was done on production.
Then checked and found that now issue has been fix for Nokia NodeB(405) which has been now imported in NEP.