Has anyone else noticed a change in how the wherecontains function works? S

Jin Pheh

Certified Associate Developer

over 10 years ago

Has anyone else noticed a change in how the wherecontains function works?
Specifically if I am searching for repeated values the wherecontains now removes duplicates from the results where it used not to.
Eg:
wherecontains({a, b, a}, {a, b, c})
I expect this to return [1, 2, 1] however it now returns [1, 2].

If this is the desired behavior does anyone know how I might get the first result (IE: [1, 2, 1]) short of using an apply function? (I'm manipulating large arrays and I'd prefer to use a set function instead of an iterative one)...

Discussion posts and replies are publicly visible

Parents

0 Eduardo Fuentes
Appian Employee
over 10 years ago

- Just tested in all versions from 6.6.0 to 7.7 and it has always worked this way, without duplicates in the result.
- I don't' have any other set function in mind that would help in this case on top of my head but can you describe the use case to see if there's another option other than looping?

I'll also let other throw out ideas on this one, but wanted to clarify that the behavior has been the same since the beginning of this function to avoid confusion
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eduardo Fuentes
Appian Employee
over 10 years ago

- Just tested in all versions from 6.6.0 to 7.7 and it has always worked this way, without duplicates in the result.
- I don't' have any other set function in mind that would help in this case on top of my head but can you describe the use case to see if there's another option other than looping?

I'll also let other throw out ideas on this one, but wanted to clarify that the behavior has been the same since the beginning of this function to avoid confusion
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data