Tips and tricks to handle dateTime formats in Mule 4

We generally come across various scenarios while developing integrations, wherein we have to deal with multiple formats of date, time, or DateTime. Sometimes source systems can send date data in only one format which may or may not be accepted by target systems, which we have to handle using dataweave expressions. In this blog, we will be going through a couple of generic scenarios which we come across frequently. For example, if we use now() in dataweave, we get an output as below.
DataWeave expression:
%dw 2.0
output application/json
---
now()
Output:
"2021-12-12T14:27:48.064709Z"
The above output is in the format of DateTime, and from this, it is easy to convert or extract and date or time values.

Scenario #1

What if we get date time in some different format, for e.g. "2021/12/12 14.27.48" and we just need to extract date and time in a different format as "12-12-2021 14:27:48". The best way is to cast the input date string to LocalDateTime by providing format and then convert to the string by providing the desired format.

DataWeave expression:
%dw 2.0
output application/json
---
"2021/12/12 14.27.48" as LocalDateTime {format:"yyyy/MM/dd HH.mm.ss"} as String {format:"dd-MM-yyyy HH:mm:ss"}
Output:
"12-12-2021 14:27:48"

Scenario #2

Sometimes, we have to insert dateTime to databases like SQL Server, Oracle database, etc. The generally accepted format for the database date column through Mule4 is "yyyy-MM-dd HH:mm:ss"

DataWeave expression:
%dw 2.0
output application/json
---
now() as String {format:"yyyy-MM-dd HH:mm:ss"}
Output:
"2021-12-12 14:27:48"

Scenario #3

What if we want to extract year and append Y in the end to output for example "2021Y". If we use the format as "yyyyY" or "yY", the output will come as a year repeated 2 times. The reason is y or Y is formatting character. If we want explicit Y to be displayed, one way could be to extract Year and then concatenate year with Y. Another way is to escape the formatting character by enclosing it in ''. For example:

DataWeave expression:
%dw 2.0
output application/json
---
now() as String {format:"yyyy'Y'"}
Output:
"2021Y"

Tabular representation of various formatting characters that can be used.
DateTime: "2021-08-09T15:37:29.519633+05:30"
Character(s) Description Example
y Year of the era (BCE or CE) or calendar year 2021
yy Calendar Year limit to 2 digits 21
Y Week based year 2021
YY Week based year limit to 2 digits 21
u Calendar Year without era (BCE or CE) 2021
uu Calendar Year limit to 2 digits 21
M The month with no leading 0 8
MM The month with leading 0 08
MMM Month name with 3 characters Aug
MMMM Complete Month name August
d Day of the Month 09
D Day of the Year 221
E Abbreviated day of the Week Mon
EEEE Day of the Week Monday
h An hour in 12 hour clock (1-12) 03
H An hour in 24 hour clock (0-23) 03
m Minute of the hour 37
s Second of the Minute 29
S Fraction of the second 5
a AM/PM PM
Z Timezone Offset +0530
ZZZZ Timezone Offset GMT+05:30

References:


Please share your valuable feedback 😊😊😊


-

Comments

Post a Comment

Popular posts from this blog

DateTime formatting using xp20:format-dateTime ()

xs:dateTime Format In XML, we generally use xs:dateTime(xs:xmlns="http://www.w3.org/2001/XMLSchema") data type to store date time data. The generic representation of date time, that is supported by xs:dateTime in xml: YYYY-MM-DDThh:mm:ss[.SSS][Z|(+|-)hh:mm] Example :  2019-09-11T10:16:31.943+05:30 Code Description Example YYYY represents a 4-digit year 2019 MM represents a 2-digit month 09 DD represents 2-digit date 11 hh represents 2-digit hours 10 mm represents minutes in 2-digits 16 ss represents seconds in 2-digits 31 SSS represents milliseconds 943 T represents time separator T Z represents UTC time zone or 0 time zone offset (+|-)hh:mm represents time zone offset +5:30 Few more valid examples : 2019-09-11T21:32:52, 2019-09-11T21:32:52+02:
Read more

Create Delimited String from XML Nodes and Vice Versa in SOA 12c

A delimited string is a string representation of data separated by a delimiter(e.g. ","). A simple representation of the delimited string will look like. Delimited String Examples Sample-1-- Delimiter as ","        Value1,Value2,Value3   Sample-2-- Delimiter as "|"        Value1|Value2|Value3 If we want to represent the above set of delimited values in the form of an XML document under some root and parent tag. The representation will look like this. XML Example <root xmlns="http://test.com/sample/xml">   <Values>     <value>Value1</value>     <value>Value2</value>     <value>Value3</value>   </Values> </root> Sometimes we may need to convert values coming in delimited string to an xml document or vice versa. Since delimited string is similar to csv format. We can create
Read more

Import and Export MDS artifacts in SOA 12c

Image
Oracle SOA-MDS (Metadata Store) repository can be used to access artifacts that can be shared among various SOA composites. For example, we have one common schema for a business fault that is consumed by various applications. Instead of having a localized copy of that schema file in each SOA composite, we can have it in a centralized repository (SOA-MDS). Another benefit of using SOA-MDS is that we can change the file at runtime and need not redeploy the complete code. While developing SOA composites, we use SOA design-time repository, later these changes can be synced to the SOA servers. In this article, we will discuss 2 ways to sync the artifacts available in the SOA design-time repository and the SOA servers. Establishing the connection to SOA-MDS in Jdeveloper. Using SOA em console or Fusion Middleware control console. Moving a file between SOA composite to SOA design-time MDS repository Let's assume, we created a businessFault.xsd which wi
Read more