vspatil2211
(Vishwanath Patil)
January 14, 2026, 5:10pm
1
I have created following transform for converting NonEmployee source account date from ISO8601 to yyyy-MM-dd.
But its Not working on Identity profile, the date value attribute on the identity preview and also on the identity after processing is showing blank.
{
"name": "NELM DateFormat Transform",
"type": "dateFormat",
"attributes": {
"inputFormat": "ISO8601",
"outputFormat": "yyyy-MM-dd"
},
"internal": false
}
Note : Also tried replacing the ISO8601 with actual format string “yyyy-MM-dd’T’HH:mm:ss.SSSZ” for the inputFormat but still the date attribute on the identity is showing blank (“–” ) in preview as well as on the identity after refreshing with “process identity” option.
Hi, @vspatil2211 .
Hope you are doing good.
Your transform looks good.
If you take the transform out and try a preview, what date exactly do you see? “yyyy-MM-dd’T’HH:mm:ss.SSSZ”?
Rohit_Sahu
(Rohit Sahu)
January 15, 2026, 5:24am
3
Hi @vspatil2211 ,
Welcome to the Developer Community!
Your transform looks good, could you please recheck on the input date format of the NELM source.
3 Likes
vspatil2211
(Vishwanath Patil)
January 15, 2026, 1:51pm
4
Thanks Kevis for the review and update, below are the date values without applying the transform
Start Date: 2025-11-21T18:30:00Z
End Date: 2026-11-27T18:30:00Z
vspatil2211
(Vishwanath Patil)
January 15, 2026, 1:52pm
5
Thanks Rohit for the review and update, below are the date values without applying the transform
Start Date: 2025-11-21T18:30:00Z
End Date: 2026-11-27T18:30:00Z
Tursun
(Shawn Tursun)
January 15, 2026, 3:04pm
6
Hi @vspatil2211
The raw date values 2025-11-21T18:30:00Z do not match what ISO8601 expects. ISO8601 expects milliseconds yyyy-MM-dd’T’HH:mm:ss.SSSZ. From my understanding parser can’t match the input and transform returns null and preview shows blank.
Can you try bellow as inputFormat that matches your value.
{
“name”: “NELM DateFormat Transform”,
“type”: “dateFormat”,
“attributes”: {
“inputFormat”: “yyyy-MM-dd'T'HH:mm:ssX”,
“outputFormat”: “yyyy-MM-dd”
},
“internal”: false
}
X here because input ends with Z, and X is the ISO-8601 timezone pattern that correctly parses Z as UTC.
If values are always ends with literal Z
{
“name”: “NELM DateFormat Transform”,
“type”: “dateFormat”,
“attributes”: {
“inputFormat”: “yyyy-MM-dd'T'HH:mm:ss'Z'”,
“outputFormat”: “yyyy-MM-dd”
},
“internal”: false
}
1 Like
Hi @vspatil2211 ,
Thank you for the feedback.
Please try like this:
“name”: “NELM DateFormat Transform”,
“type”: “dateFormat”,
“attributes”: {
“inputFormat”: “yyyy-MM-dd’T’HH:mm:ss’Z’”,
“outputFormat”: “yyyy-MM-dd”
},
“internal”: false
}
Rohit_Sahu
(Rohit Sahu)
January 20, 2026, 7:49am
8
Hi @vspatil2211 ,
Thanks for the response. Please try the below transform as it’s working for me.
{
"name": "NELM DateFormat Transform",
"type": "dateFormat",
"attributes": {
"inputFormat": "yyyy-MM-dd'T'HH:mm:ss'Z'",
"outputFormat": "yyyy-MM-dd"
},
"internal": false
}
Regards,
Rohit Sahu
2 Likes