Are there any known issues with the filternulls() function in Appian 7.3? I not

Chris over 10 years ago

Are there any known issues with the filternulls() function in Appian 7.3? I noticed these results today:

=filternulls({if(1=1,null(),now()),null()}) > ={"3/2/2015 5:10 PM EST"} (correct)
=filternulls({if(1=2,null(),now()),null()}) > = {,} (incorrect?)

Additionally, as in the function instructions:

filterNulls({1,2,null,5,null}) > {1,2,5} (correct)
filterNulls({"1","2",null,"5",null}) > {1,2,,5,} (incorrect)

However the function is supposed to allow any type array. Has anyone ran into this issue?

Discussion posts and replies are publicly visible

0 Chris over 10 years ago

Sorry my first 2 expressions were swapped, should read:

=filternulls({if(1=2,null(),now()),null()}) > ={"3/2/2015 5:10 PM EST"} (correct)=filternulls({if(1=1,null(),now()),null()}) > = {,} (incorrect?)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Conor Cahill
Certified Lead Developer
over 10 years ago

instead of filternulls() you can use reject(fn!isnull,{array}) to achieve the same result. Not sure what is happening with the filternulls() function.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel