Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 223 of 808  Not logged in ELOG logo
    icon2.gif   Re: calculate diff of 2 date(s), posted by Alex Kühnel on Fri Sep 30 11:21:44 2016 
I found the solution in the forum :-)

subst Einsatzzeit = $shell(/usr/local/elog/diff.sh \"$Einsatzbeginn\" \"$Einsatzende\")

and diff.sh is
    icon2.gif   Re: calculate diff of 2 date(s), posted by Alex Kühnel on Fri Sep 30 11:25:08 2016 
is ist possible that subst only works for the initial create of a logbook entry? when I change/edit one of the parameter "Einsatzbegin"
or "Einsatzende" the "Einsatzzeit" is not changed.

regards
    icon2.gif   Re: calculate diff of 2 date(s), posted by Stefan Ritt on Fri Sep 30 12:33:38 2016 
There is the "subst on edit = ..." option you should use in addition.

Stefan




Alex
    icon2.gif   Re: calculate diff of 2 date(s), posted by Alex Kühnel on Mon Oct 3 10:01:53 2016 
thx!




Stefan
Ritt wrote:



There is the "subst on edit = ..." option you should use in
icon3.gif   Is there a way to export logs, posted by Alex Kühnel on Mon Oct 3 10:02:36 2016 elog_export.JPG
hello

Is there a way to export logs from elog (for example after I have selected a filter) to txt or csv...

I found the "Download" attribute but this works for only one elog entry...
    icon2.gif   Re: Is there a way to export logs, posted by Alex Kühnel on Mon Oct 3 10:18:19 2016 
shame on me, there is a way!

I can search with find and then export as csv file

/alex
icon5.gif   Datetime format with elog client, posted by Alan Grant on Wed Oct 26 16:39:38 2016 
What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the
field's data parameter).

I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0
    icon2.gif   Re: Datetime format with elog client, posted by Alan Grant on Wed Oct 26 21:41:42 2016 
UPDATE:

As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when
I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including
ELOG V3.1.5-3fb85fa6