Firstvalid transform is not working on provisioning policy, I tried to create email based on two combination like business [email protected] if business names are not available then we have to use regular firstname and lastname from identity profile but it seems to be non working, has anybody face similar challenge??
Hey, I understand that we need to use technical names in transform, that was some typing mistake while indenting, but it’s not working on using technical names even. I corrected now, it seems first valid is not working on provisioning.
In your case, the FirstValid transform will not work because it checks for null values, meaning it will retrieve a value from the Concat transform each time. Instead, I recommend trying the following transform, as I hope it will work for you.
Your first value will always return something, so it will never fall back to your second value. If you want to check for individual null attributes, then wrap each attribute in a “firstValid”. Also, it’s generally best to include the “ignoreErrors”: true argument to your firstValid transforms:
Hey everyone, Thanks for your provided transform and guidance regarding different approaches here all provided transform worked but as in our requirement first valid is properly implemented, @Rohit_Sahu@KevinHarrington@Santhakumar all your solutions perfectly worked, there is no option to choose multi solution for this post. but all provided transform worked
Hey @Rohit_Sahu@KevinHarrington@Santhakumar can we add unique logic within this transform let suppose same name of person exist already then it should be appended with unique counter at the time of provisioning in this format [email protected]
firstname.lastname@demotest.com
Hey, But there also I need to use the same logic to check first for business names if not then it should pick regular names, do you think whether under username generator can we define the first valid transform to check for pairs?
