Difference beteween not() and false() in Xpath

Question

Difference beteween not() and false() in Xpath

0

Today, I encountered an issue in my code. I needed to retrieve evaluations with at least one unresolved pending. However, my initial approach using "not()" did not work as expected. I resolved the issue by changing "not()" to "false()" in my microflow.

The problem with using "not()" in this XPath was that it only returned evaluations that didn't have any resolved pending.

I addressed this problem by using the "false()" function. As a result, I was able to retrieve all evaluations that had at least one unresolved pending.

asked 2023-08-15

Charly Ventura

3 answers

Johan Flikweert · Answer 1 · 2023-08-24

So, what's your idea?

Charly Ventura · Answer 2 · 2023-08-18

Yes, John, perfect!

Johan Flikweert · Answer 3 · 2023-08-16

It's indeed a functional difference you clearly point out, which is intended.

If you want to retrieve evaluations that don't have any resolved pending, you can use the first xpath. If you want to retrieve evaluations that had at least one unresolved pending, you can use the second.