Receiving "invalid operand type" on "increased by over" and "decreased by over" triggers on a rule

Fix in next release.

5 Likes

Is this now fixed? I am getting very similar error messages when using the simple 'decreased' trigger on a custom attribute (I have tried setting the attribute as an integer and as a floating number with a decimal point in the driver but errors both ways).

I am running 2.3.6.145 which says it has fixed this for "decreased by over".

Any thoughts welcome ...

It is fixed for me. 2.3.6.146 resolved it.

Please show the rule.

Yes, I have updated and all seems to be ok now.
Thanks