LogViewPlus Support

Data store column mapping bug?

https://www.logviewplus.com/forum/Topic545.aspx

By Blaž Cegnar - 4 Jun 2020

I am trying to add an SQL table as a data store and map its columns but the mapping does not work as expected. Here is the setup:


Already at validation window the columns are not mapped, but maybe this is expected behaviour:


This is when I open the log view:


Message column is empty. If I set a custom string column name (first picture) it gets ignored completely.
By LogViewPlus Support - 4 Jun 2020

Hi Blaz,

Thanks for reporting this issue.

What version of LogViewPlus are you using and what database are you trying to connect to - Sql Server?  Also, what is the datatype for the 'Text' field?

I would recommend installing the latest BETA release.  There were a number of database related changes in this release.  You can download it from: https://www.logviewplus.com/download.html

Also, if you move to the 'File Transfers' tab in the bottom left corner of the application and right click, you should see a 'Show Transfer Log' command.  Does this log have any information?

Thanks,

Toby
By Blaž Cegnar - 4 Jun 2020

I have v2.4.30.0.
Yes, SQL server. This is the table design:


I attached "File Transfers" log file.

I will try with the beta version.
By Blaž Cegnar - 4 Jun 2020

I can confirm the same issue in v2.4.31.0
By LogViewPlus Support - 4 Jun 2020

That's strange. I just ran the BETA version to confirm the SQL connection - everything looks OK.  Our test DB uses a nvarchar(max) column - so I do think the column definition is the problem.

Anything in the transferlog file after the version update?
By LogViewPlus Support - 4 Jun 2020

Sorry - just noticed from your screenshot that the log entry does contain a message.  I assume the log entry is fine and the problem is just with the data appearing in the column?
By Blaž Cegnar - 4 Jun 2020

Yes, the data is not appearing in the column.

But it does work in this example:


If I put "Message" as the String Column Name then the column is empty.

By LogViewPlus Support - 4 Jun 2020

Ok.  I am glad you have found a temporary workaround.  Let me look into this and get back to you.

Thanks for reporting this issue!

Toby
By LogViewPlus Support - 7 Jun 2020

Hi Blaz,

I was able to recreate and fix this issue in the latest BETA version of LogViewPlus - v2.4.32.  You can download the BETA from: https://www.logviewplus.com/download.html

Thanks for bringing this problem to my attention!

Toby
By Blaž Cegnar - 8 Jun 2020

Great, it works now. Thanks!
By LogViewPlus Support - 8 Jun 2020

Glad to hear it - thanks for letting me know!

Please let me know if you have any further questions or issues.

Thanks again,

Toby