LogViewPlus Support » LogViewPlus Support » Help & Support » Next button is disabled

Next button is disabled

hgneoh — Sun, 01 Feb 2026 10:29:32 GMT

Why the Next button is grey out? Which field am i missing?

RE: Next button is disabled

LogViewPlus Support — Sun, 01 Feb 2026 10:29:32 GMT

Flattening the XML data isn't something that is supported by default. You could use standard Message Parser, but in this case I think you are going to be limited because the data is so complex.

A better alternative would be to write a custom extension. I would suggest using a Custom Message Parser. Our example code should provide a good head start for this use case.

Hope that helps,

Toby

RE: Next button is disabled

hgneoh — Sun, 01 Feb 2026 09:36:26 GMT

Thanks, Toby! Right now, the application is parsing the entire SECSData block into a single 'Message' column. Is it possible to flatten this structure? I would like to extract the nested fields (like TaskName, EPTState, and CEID) into separate columns for detailed analysis.

RE: Next button is disabled

LogViewPlus Support — Fri, 30 Jan 2026 14:39:11 GMT

Thanks for the update.

The correct way to parse this file would be to use the XML Parser and not the default PatternParser.

Unfortunately, the XML parser currently does not support parsing child nodes collectively. It only supports text nodes. I have addressed this issue, so this functionality will be supported in the next release.

Beginning with the next release (scheduled for Feb), you should be able to parse the file with:

[code]<SECSMessage time="%d">
<SECSData>%m</SECSData>
</SECSMessage>[/code]

Hope that helps,

Toby

RE: Next button is disabled

hgneoh — Fri, 30 Jan 2026 11:57:01 GMT

I got error by using parser configuration dialog too:

RE: Next button is disabled

hgneoh — Wed, 28 Jan 2026 01:12:05 GMT

Here you go. The ideal here is to extract all the SECSMessage as individual log entry, then the log message content would be those enclosed in SECSData tag.

RE: Next button is disabled

LogViewPlus Support — Tue, 27 Jan 2026 18:41:19 GMT

Hi,

Thanks for bringing this issue to my attention. It looks like you have the information needed to continue (primarilly the timestamp). Are you able to share a log entry with the parser configuration shown? This would allow me to recreate the issue locally.

In the meantime, I would recommend ignoring the Parser Wizard and attempting to use the parser configuration shown directly using the standard parser configuration dialog.

Hope that helps,

Toby