I haven't found anything in the forums about this. Apologies if its a duplicate.

I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work. 

Currently looking to do some updates to one of the instances with the Date Type setting.

We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.

Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).

However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.

Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?

Syntax manual didn't help much for this issue.

 Hi Garret,

Why cannot you just use $entry time ?  It uses the date that the entry was made which appears as the first line of every elog entry -

[Sorry for mis-post, just discovered cannot put the 'dollar at' control set in an entry]

MID: 12458
Date: Fri, 07 Sep 2012 17:22:06 +0100
In reply to: 12453
 

You can use 'Time format = ' to get the date to display in the format you like.  You will see I have posted an issue about 'Date format = '.  I mention this because in trying to understand what was happening, I too had a case where all the dates were showing as the same in a thread.  I suspect your 12/31/1969 was due to the entries as being read were non-existant or blank.

Of course I may have mis-understood your requirements.

 I haven't found anything in the forums about this. Apologies if its a duplicate.

I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work. 

Currently looking to do some updates to one of the instances with the Date Type setting.

We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.

Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).

However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.

Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?

Syntax manual didn't help much for this issue.

Hi Stefan,

I have observed following behavior when I move entries from one logbook to another:

1. The first entry in "Open" get ID "1"
2. When I move this Item to "Closed", it will keep ID "1" as I have used "Preserve IDs = 1"
3. A new entry in "Open" gets ID "1" again
4. When I move this item to "Closed" it will overwrite the previous ID "1" in "Closed"
5. A new entry in "open" gets ID "1" again....

Every new entry in "Open" will get the next higher ID Number related to the highest available ID number/entry in "Open".

Upon "move to Closed", the previous entries in "Closed"will be overwritten.

Is there a way to prevent the usage of a previously used ID Number when entering a new ID?
I.e. If an entry with ID "1" has been used in "Open" and moved to "Closed", have the next entry in "Open" use ID "2"?

Kind regards,

Barend

 Hi Barend,

The counting of entries, or even "tickets", only works within a particular logbook.  If you archive a set of entries to another [archive] logbook, the archived set disappears from view of the original logbook.  Should that entry, from logbook to archive, be the *latest* thread, then there is the danger of over-writing message ID, Ticket No and the like.

My policy to prevent the problem is to archive only threads that are say (depending upon use) a month after last entry..

I generally consider using the ID as ticket number a bad idea. The ID is the "primary key" (in terms of database language), and must be unique inside a logbook. So when moving entries between logbooks, there will be always problems.

Why don't you define an attribute "Ticket ID" and use that one? That won't change when you move the entry between logbooks:

Attributes =  Ticket ID, Subject, ...
Preset Ticket ID = ID-#####

I have tried to use the "Ticket ID" approach and with each new entry this Ticket ID is indeed increased automatically...

But when the last Entry (with the highest Ticket ID i.e. ID-0009) is move to another Logbook, the Ticket ID in the next new entry will be "ID-0009" again (based upon the last previous entry "ID-0008").

So this appraoch will also re-produce duplicate Ticket IDs.

Is it possible to have the Ticket ID preset with value based upon the Date & Time of the entry? Instead of holding a Date/Time format, use a calculated numeric format?

This way, each new entry will have a truely unique Ticket ID.

Thanks & Regards, Barend