Dear @Indrasan Yadav,
After reviewing the database, error reports, and implemented logic, we identified the following:
1. Upon checking the database, I found that the NE licenses were imported into NEP on 7-DEC-2024, which is the date this XML was imported. Additionally, the number of NE licenses imported is 51,588
2. As per the logic implemented, the warnings you are getting in the error report “License: XYZ is not imported due to: Config. has invalid value It must be a number” and “License: XYZ is not imported due to: Usage. has invalid value It must be a number” do not prevent the import of NE Licenses.
However, these warnings are misleading. Therefore, we have updated the warning to “License XYZ: Config has invalid value, It must be a number”.
Patch is needed for the warnings update: 3.7.1.635
In conclusion, the NE licenses were successfully imported into NEP, and the warnings in the error report do not stop the import process.
Regards,
Mustapha Al Hage
Dear @Khaled Khalil,
Could you please assign a DEV resource to investigate and resolve the issue described below?
I validated the data in NEP on platform .14 after the XML (2024-12-05-08.21.07_ZainKsa) was imported. During the validation, I found the following issue related to the licenses data, which were not imported into NEP:
1. The licenses are available in the XML, as shown in the snippet below for reference.
2. When I reviewed the error report, I did not find any errors related to this issue. However, I observed a warning message under the "Category Validation Failed" section concerning config and usage. Please note that these config and usage details are not required in this case, as they are not present in the XML.
3. Similar issue was also faced in Huawei case which was fixed by @Diana Hamdouche.
Best regards,
Indrasan