Question4Replies145Views×Close popoverPriyanka K.N (PriyankaKN) Accenture , Netherlands Accenture , Netherlands NL View Profile PriyankaKN Member since 2014 13 posts Accenture , Netherlands Posted: April 12, 2017Last activity: April 15, 2017Posted: 12 Apr 2017 3:54 EDTLast activity: 15 Apr 2017 14:18 EDT Closed Unexpected Date format generated in DB records when OOTB function is usedBelow is the OOTB function usedEMAIL_SENTDATETIME = @(Pega-RULES:DateTime).FormatDateTime(@(Pega-RULES:DateTime).CurrentDateTime(), "d-MMM-yyyy HH:mm:ss", "America/New_York", "")Issue Faced : We are seeing records for DB in Column EMAIL_SENTDATETIME as "11-abr -2017" instead of "11-Apr-2017"Any suggestions regarding why "11-abr-2017" is getting recorded in DB? Data Integration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 3 years agoPosted: 12 Apr 2017 4:42 EDT×Close popoverSantanu Bhattacherjee (Santanu) PEGA Manager CRM - Field Service Pegasystems Inc. IN View ProfileSantanu PEGA replied to PriyankaKNHello At my end I cant see the issue happening in my 7.2.2 system. Attached the image. Have you tried running tracer and see whether any error coming there or not? Also what is your system locale ? Posted: 3 years agoPosted: 12 Apr 2017 5:56 EDT×Close popoverPriyanka K.N (PriyankaKN) Accenture , Netherlands Accenture , Netherlands NL View ProfilePriyankaKN Accenture , Netherlands replied to SantanuHi Santanu , Thanks for your reply We are currently using 6.3 SP1 and that issue is not very persistent , it is only occuring for very few records( as of now for 4 records) in Production and it is working fine in rest other environments. Posted: 3 years agoPosted: 12 Apr 2017 7:20 EDT×Close popoverLaurence Brannigan (LaurenceB_GCS) PEGA Senior Software Solutions Engineer PEG GB View ProfileLaurenceB_GCS PEGA replied to PriyankaKNBased on the characters alone I'd be inclined to try testing this with an operator who is logged in with a Spanish locale, and see whether you then reproduce the same behaviour more consistently. If so, you may choose to specify the locale when you make the call to FormatDateTime Posted: 3 years agoPosted: 15 Apr 2017 14:18 EDT×Close popoverSantanu Bhattacherjee (Santanu) PEGA Manager CRM - Field Service Pegasystems Inc. IN View ProfileSantanu PEGA replied to PriyankaKNHi Even I also suspect some locale related stuff here. Which locale your users are using when they are facing the issue and also what is the browser locale?