Re: Timestamp default value - weird problem

Interesting, there is a discrepancy at least on the .def files. I'll compare the XMLs when I'm on a larger display. On 2 May 2017 at 15:58, Dave Barber wrote: > Hi LJ - I'll try that with the form exports - but interestingly, I've > found one copy on a server with

Re: Timestamp default value - weird problem

Hi LJ - I'll try that with the form exports - but interestingly, I've found one copy on a server with history and the data in that field changed after the migration to 9.1 - on 7.6.04 it was just a regular time stamp in a text field, after the upgrade it became a UNIX date integer stored in a text

Re: Timestamp default value - weird problem

Dave, maybe a copy of logs of the workflow or something...maybe a copy on a server that's not working, but working in a copy of the form...screen shots of the workflow in question...but if it's a default...there is no workflow try thisexport two copies of the form...one that's working,

Timestamp default value - weird problem

All, We have a form, used as part of a notifications system, it has a 255 character field with a default value as $TIMESTAMP$. So in theory it should store a value 02/05/2017 08:13:40 (UK/GMT date format) We've recently gone through a series of upgrades, from Remedy 7.6.04 (on Solaris) to