How to filter negative values from readonly grid

Question

I have a requirement to filter negative values from readonly grid and It needs to get configured from expression rule but Im not able to filter the negative values. 
 I tried using "<" as operator for that particular field but still not filtering out. 
 
 please help me achieve this

Mike Schmitt · Accepted Answer

appian.user said: you mean to say i have to use sum() add 1 to selected value ? 
 sum() doesn't really play into this. you can simply add 1 to the user-entered value when feeding it into your queryFilter. If you're not sure how to do that, you can post the actual code from your queryfilter and i can tell you how to modify it. Generally you'd put something like, 
 a!queryFilter( field: "latitude", operator: "<", value: ri!userSelectedValue + 1 )

Mike Schmitt · Answer

appian.user said: 42 then grid will display value between 41 and 43? 
 If the user enters an upper value of 42 and you add 1 to it when actually performing the filter, as in my example code above, and the operator is "<", that means any values less than 43 will be returned, up to and including i.e. "42.999" etc. For the lower-end filter you would want to use the ">=" filter and just pass the user's original value, i.e. it would start matching values at 41 and all incrementals above that (41.00001, 41.3, 41.9, 42, 42.5, etc).

Mike Schmitt · Answer

appian.user said: can you please tell me how can I apply on my code 
 I'm not sure I understand. If you're allowing the user to enter decimal filter values, the code you have here looks like it'll work basically as expected. 
 If a user enters "41.8" for instance on the "From" value, wouldn't they expect to ONLY see values from "41.8" and higher? What are you expecting to happen that isn't happening? 
 As an aside, one other thing I'd point out is, you shouldn't really need to do this bending-over-backwards to switch to the "between" operator; you can just use the "from" and "to" individual filters by themselves and when a user has both entered, they'll simply both apply , functionally taking care of a "between" operation on their own, and without having to have so many conditions on all the operators.

Mike Schmitt · Answer

I mean you can generally replace the "between" operation just by having "from" and "to" operations separately that both activate when they're required - when both of them activate at the same time, they will "stack" with each other (presuming that your logicalExpression is using the "AND" joiner), and essentially behave like the "between" operation. So it's redundant. But I assume this does not necessarily answer your main question here - just a tip for efficiency in coding filters. 
 appian.user said: you mean to say my operator for both from to is correct only i have to remove between condition and to remove applywhen condition to specific from to else nothing to change right?

Mike Schmitt · Answer

appian.user said: example 41.4 and 42.3 then grid should display as 41.5, 41.9, 42.2 but not 42.9 
 This sounds confusing to users (i.e. entering "42" would match "42.9", but entering "42.1" wouldn't match anything higher than 42.1) - however it should be possible to code. in your filter logic you could take steps to determine whether the entered value is a non-decimal value (note i'm just talking about the value, not the data type), and if so, add 1 to the value when executing the filter; otherwise, don't add anything to the value. 
 As far as how to check whether the entered value is a non-decimal? it's not straightforward, usually there are tricks using the various math functions. Maybe "floor(ri!num) = ceiling(ri!num)", meaning if the number rounded up to the next integer is the same as the number rounded down to the next integer, which would only be true (afaik) when the starting number is already an integer.

Mike Schmitt · Answer

Please share the actual code you've tried so we can make informed comments. Generally an a!queryFilter(), when filtering on a numeric value, should accept the "<" operator just fine, but any number of other things could have gone wrong before it even gets that far, and it's hard to guess without seeing exactly what you've tried and exactly what went wrong.

Kumar Agniwesh · Answer

are you trying to filter values which does not match a condition. Example :- Filter values which are not equals to 1 or "ABC", if so then using <> operator might works for you. 
 
 Also you can use Appian query editor on top side of expression rule for guided development for writing these type of query.

Prasanta Paul · Answer

Please ignore the field, I have used (-) in contact number just for testing purpose and here is the result. Maybe it will be helpful for you.

Mike Schmitt · Answer

if you want a value like 42.2 to be included then your "to" filter entry should be 43. Or you could just override the filter value and add 1 to whatever the user enters, so it would match all values up to the next higher integer (you'd just need to test it well to make sure different corner cases work like you expect).

vigneshkumarradhakrishnan · Answer

Hi, please try the below code, as mike said increment that end value & check both < and >= in query filter with ri!latTo+ 1 and remove the extra query filter "between" query filter. Hope this will works for you.

a!queryFilter(
field: 'recordType!{9441efd7-521a-4695-82a7-d661a237c67d}.fields.{499d2d44-21c8-41dc-a3be-2dbd3ee0356f}',
operator: ">=",
value: ri!latFrom,
applyWhen: and(
not(rule!APN_isEmpty(ri!latFrom)),
rule!APN_isEmpty(ri!latTo)
)
),
a!queryFilter(
field: 'recordType!{9441efd7-521a-4695-82a7-d661a237c67d}.fields.{499d2d44-21c8-41dc-a3be-2dbd3ee0356f}',
operator: "<=",
value: ri!latTo + 1,
applyWhen: and(
not(rule!APN_isEmpty(ri!latTo)),
rule!APN_isEmpty(ri!latFrom)
)
),

Kumar Agniwesh · Answer

based on your screen shot, I am assuming when user is typing 42 then you need to show the values from 41 till 42.99, if so you would need to run the filter after incrementing the typed value by 1. in this case it is 43.

How to filter negative values from readonly grid

Top Replies