I am attempting to use Account Attributes to trigger a lifecycle change. If “On Leave” says true, it should trigger the LCS change to On Leave. Workday has been configured and is passing the flag for “on leave.” The issue is that the transform doesn’t know how to handle a null value.
How do I fix the table to interpret empty or null values as false/no?
can you try adding “ignoreErrors”: “true” and put a default value of No
jesvin90
(Jesvin Joseph)
April 16, 2024, 3:32am
3
Hi @davidballew ,
Have you considered using a simple lookup transform instead.?
{
"name": "On Leave Fix",
"type": "lookup",
"attributes": {
"table": {
"0": "No",
"1": "Yes",
"default": "No"
}
},
"internal": false
}
You can then map this transform to the attribute in the Identity profile.
The default parameter will take care of the null values.
1 Like
You can use a “lookup” transform instead of “replaceAll” as @jesvin90 said.
Else, you can include a firstValid transform in input field, as it takes care of null values. And then, in table you can use “ValueOfNull”: “No”
{
"name": "Test",
"type": "replaceAll",
"attributes": {
"table": {
"1": "Yes",
"0": "No",
"NONE": "No"
},
"input": {
"attributes": {
"values": [
{
"attributes": {
"sourceName": "Your Source name",
"attributeName": "Attribute Name"
},
"type": "accountAttribute"
},
"NONE"
]
},
"type": "firstValid"
}
}
}
1 Like
Shouldn’t this have a line for Periodic Refresh? The On Leave flag is something that can change from day to day.
nandambk
(Karthik Nandam Balraj)
April 16, 2024, 3:26pm
6
yes, refreshPeriodicFlag is needed when ever you needed a transform to be evaluated everyday
system
(system)
Closed
June 15, 2024, 3:26pm
7
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.