Log Entries by Date Range

Are they custom fields that are stored in the Logs table or are they stored in virtual tables? If they're stored in the logs table and you're on PS 6, you can use the new custom field api to get to them instead of using the PVSIS. Some of those PVSIS's don't work with tlist_sql, but I'm not sure about the custom log one. If the fields are in virtual tables someone else may have to chime in as I haven't pulled anything from virtual tables via sql.

Matt

Should be possible. I added a pdf to the site called tlist_sql basics that you can find at http://www.powerdatasolutions.org/content/tlistsql-basics that should help with how to modify the page or other pages. Basically what you'll want to do is add a column heading, add a reference to the field in the select part of the sql, and then a reference to the field in the output area.

The only thing that may cause problems is if one thing is stored in the field but you want something else to appear. Then you may need to use what's called a case statement in the select to set the output or use the if.test command in the output. The pdf covers the if.test command.

Matt

I've seen that error before on a page - it's basically an Oracle error and should only happen when the page first loads because in the url there's nothing after html like there is after you make selections and click submit. The error happens because the tlist_sql executes when the page is first loaded and without some of the gpv stuff it uses it gives an error that it's missing an expression to use. I had it happen on another page and had to add an if statement before the tlist_sql to say if the url was blank after the html part then skip the tlist_sql. I'll add that and upload a new version and that should make the error stop.

Matt

(uploaded version 1.1 which should keep the DALX errors from appearing. The problem was in the sql that creates the heading rather than the sql in the table output.)