DATECOPYOPT

[David Teh]

Hi folks,

In the translation, DATECOPYOPT has this ‘Time Options’ function which should not come into play as long as source sends CCYYMMDDHHMMSS, right?

I have a weird situation where one XLT using DATECOPYOPT (with use system time) is truncating the HHMMSS of the message. Another XLT using  DATECOPYOPT (with use custom time) sends the full CCYYMMDDHHMMSS.

Not too sure why it matters since the source message sends the full CCYYMMDDHHMMSS.

Strange……..

Topic

[Anonymous]

So what is your question????

[Jim Kosloskey]

David,

Check the definition for the fields in question on the outbound variant(s).

It is possible somebody shortened one of the field lengths.

Another possibility (but I think you might have already checked for this) is there is a proc involved with one of the Xlates which is truncating the field.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[David Teh]

DATECOPYOPT is just guessing the cause.

Question is how the truncation occurred.

Thomas G Rioux wrote:

So what is your question????

[David Teh]

Hi Jim,

Thanks!

The HL7 variant is long enough to accomodate the full length.

Before posting, I did test without the proc, it was truncated as well….Strange.

I’ve changed the XLT DATECOPYOPT to use custom time instead. It works fine now, though it still puzzles me why this should matter.

Hmm……………..

Jim Kosloskey wrote:

David,

Check the definition for the fields in question on the outbound variant(s).

It is possible somebody shortened one of the field lengths.

Another possibility (but I think you might have already checked for this) is there is a proc involved with one of the Xlates which is truncating the field.

Jim Kosloskey

[David Teh]

Latest ‘weird’ discovery…🙂

With certain XLTs with DATECOPYOPT (using custom time), I still face the truncation issue.

What is weirder is (seemingly) to resolve the issue, I open up the DATECOPYOPT action properties window. I tick on ‘Add Precision’ and untick it. And click OK.

The date/time gets sent over in full.

Is this a bug?

[Jim Kosloskey]

David,

With ‘Add Precision’ on you should see the GMT offset as well as Date/Time. Do you (and is the field definition of the outbound variant long enough to contain the full DT length)?

If you do then Add Precision is doing its job.

With ‘Add Precision’ off the GMT offset is normally eliminated.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[David Teh]

Morning Jim,

The field length is long enough to accomodate but we don’t want to map the offset.

It works fine now after doing the odd ticking/unticking of the ‘Add Precision’ option. Weird!

Jim Kosloskey wrote:

David,

With ‘Add Precision’ on you should see the GMT offset as well as Date/Time. Do you (and is the field definition of the outbound variant long enough to contain the full DT length)?

If you do then Add Precision is doing its job.

With ‘Add Precision’ off the GMT offset is normally eliminated.

Jim Kosloskey

[Author]

Replies