Exports as XML does not export incidents and produces null.htm file. In the localhost log file you see the below error:
5 Jun 2023 14:25:47,634- Thread: 116 WARNING [com.vontu.manager.struts.transactions.ForbidsTransactionProxy] Aborting transaction due to exception thrown by class com.vontu.manager.report.incidentlist.IncidentListXMLExportAction.execute15 Jun 2023 14:25:47,634- Thread: 116 SEVERE [com.vontu.manager] [/NetworkIncidentListXMLExport] Unexpected error occurred while processing action15 Jun 2023 14:25:47,634- Thread: 116 SEVERE [com.vontu.manager] [/NetworkIncidentListXMLExport] Cause:com.vontu.manager.system.EnforceRuntimeException: Unable to transform incident list for xml exportcom.vontu.manager.system.EnforceRuntimeException: Unable to transform incident list for xml export
(...)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:750)Caused by: java.lang.NumberFormatException: Not a number: status.201 at com.vontu.condition.sql.NumberFormatter.format(NumberFormatter.java:63) at com.vontu.manager.report.conditions.StatusOperandParser.<init>(IncidentStatusPredicate.java:159) at com.vontu.manager.report.conditions.IncidentStatusPredicate.generate(IncidentStatusPredicate.java:87)
16.0
Reports that are exported to XML in DLP 16.0 are limited to the hard-coded DLP 15.8 format. They are not customizable.
The Export as XML feature is deprecated in DLP 16.0 and will be removed in a future release. No further changes/fixes will be made for this feature. Information available in the XML exports is also available through JSON or Enforce REST API.
You can test if the below workaround works for you while you are on 16.0.x