Hi.
It does not have to be that complicated...
If the only problem is a swap of mm and dd, a simple FLTR Set-Fields should
suffice. Insert this action before you use the data in what I presume is a
Push-Fields action to the DateTime-field.
Set-Fields:
CharField = SUBSTR($CharField$, 3, 4) + "/" + SUBSTR($CharField$, 0, 1) +
"/" + SUBSTR($CharField$, 6)
Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11/12):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> You need to write a filter and update through DIRECT SQL, I have this
> experience with one of my API.
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:arslist@ARSLIST.ORG] On Behalf Of Karthick
> Sent: Tuesday, March 26, 2013 3:00 AM
> To: arslist@ARSLIST.ORG
> Subject: Pushing data from character field to date field
>
> Hi all,
>
> We have third party application were the data comes to remedy stating form and
> the date/time will be captured in character field. When the datas are moved to
> main form the date are showing different.
>
> Ex.
> Staging form
>
> Character field .
> Date/Time field - mm/dd/yyyy
>
> When the data is moved to main form it take dd as mm and mm as dd.
>
> Help me on this
>
> Our server timing is in Australia time zone
>
> Sent from my iPhone
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers
> Are, and have been for 20 years"
>
> The information in this email may contain confidential material and it is
> intended solely for the addresses. Access to this email by anyone else is
> unauthorized. If you are not the intended recipient, please delete the email
> and destroy any copies of it, any disclosure, copying, distribution is
> prohibited and may be considered unlawful. Contents of this email and any
> attachments may be altered, Statement and opinions expressed in this email are
> those of the sender, and do not necessarily reflect those of Saudi
> Telecommunications Company (STC).
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
