Ok thanks for taking the time to try it out. I definitely still show "All entries" in any case, so I will continue to try to resolve on my end and if I find the cause or solution I will share back on the forum.

First though, I noticed you ran 3.1.4 whereas I'm still on 3.1.2. I'm also on Windows Server 2016 and IE 11. Do you think any of that might make the difference?

Thanks again.

I noticed in the Change Log for 3.1.4 that there's a reference to something done with "Last default" in Sept 2018 so I think I will try to set up a Linux instance and try out 3.1.4. Regards.

Version 3.1.4, released September 26th, 2018
============================================

- Replaced sprintf by snprintf
- Changed midas.psi.ch to elog.psi.ch
- Fixed bug for redirect under two daisy-chained proxies
- Removed while(in_asend) which caused some browsers to block
- Implemented elogd.service for systemd daemon
- Implemented "max email attachment size"
- Limit max request size to 100 MB
- Allow ampersand in user names
- Added code to detect Unicode characters as HTML
- add "Email CSS URL" : use public copy of CSS for emails
- bugfix: replace hard-coded reference of "New" to loc("New")
- add "Subscription columns" : format list of logbooks for subscriptions in columns
- Added "interface" option
- Fixed crash on negative Content-Length in header
- Fixed "?npp=0" crash
- Added confirmation dialog before deleting an attachment
- Implemented "last default" to restrict quick filter display by default on the last n days
- Made header parsing case insensitive
- Switched to TLSv1_

Apart from an inline shell command that can be run with the Execute attribute, is it possible to run an external script file? I would like to run a Powershell script with the Elog attribute data parameters passed to it upon Submit New entry.

I think it was just a matter of my specific interepretation of the documentation, ie: using native OS shell commands vs any script language file containing shell commands or any app for that matter. Nevertheless I think you've answered my questiuon so it's all good. Thanks Stefan.

I have the line in my elog config to run a Powershell script when submitting a New entry. I just send an email as a test:

Execute New = "Powershell.exe -ExecutionPolicy Bypass D:\SendEmail.ps1"

Fyi, the Powershell statement itself (Send-MailMessage -From 'MeterElog@winnipeg.ca' -To 'alangrant@mts.net' -Subject 'New meter entry' -Body 'TEST' -Priority High -DeliveryNotificationOption OnSuccess, OnFailure -SmtpServer 'citygw') works fine and the email is received when running it from the Powershell ISE app directly from the same elog vm server but not from within Elog with the above statement.

I'd like to first confirm that the syntax of the line Execute New = is correct, ie, double quoting the entire command. Can anyone please confirm.

Sometimes we change the attributes in a config file for a given tab as time goes on, which naturally can get out of sync with the older data in that tab.

I can imagine some other Elog users have encounterd this too at some point so I'm wondering if there's a utilty or some way anyone knows of that I can use to parse a log file DIRECTLY to view the older data, without using the Elog GUI?

Hi John. The problem with using the Find-->Export method is that some of the Attributes for the older data are no longer shown on that screen because the Config file has since changed. That's why I'm contemplating somehow parsing the log files directly instead.

Is there any way to log child events on the detail pages for a fixed number of entries on the main page? For example, I have 15 vehicles to enter on the main page, ID'd by Vehicle Number. Within each of those entries I will be logging ongoing repair service entries with certain attributes.

So how might I design this concept without having repeating vehicle entries on the main page for every service event, and preferably without splitting the information between two linked logbook tabs?