Tips:Behavior of not() function - InfoPath Dev
in

InfoPath Dev

Tips:Behavior of not() function

Last post 10-24-2006 01:42 AM by Agni Jonnalagadda. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 10-19-2006 04:46 AM

    • hotikisu
    • Not Ranked
    • Joined on 10-20-2006
    • Japan
    • Posts 6

    Tips:Behavior of not() function

    A not() function does not do movement to expect. Even if a not() function appoints a field in an argument, I do not turn over the Bour negation of the field. A value of a not() function is always "false".

    Seemingly this looks like a bug, but it is different. The reason is so. An argument of a not() function watches existence of a nodeset.

    If you want to check behavior of a not() function, please please test next.

    (1)Make a new form.
    (2)Create table including a field, name of "field1".
    (3)Create experiment box, set a function "not(field1)".
    (4)Preview the form.
    (5)Check a experiment box is "false".Because field1 nodeset is exist.
    (6)Delete a field1.
    (7)Check a experiment box is "true".Because field1 nodeset is not exist.
    ---------------------------------------
    Yoshio Matsumoto (hotikisu)
    MVP for InfoPath, Japan
    ---------------------------------------
  • 10-23-2006 12:01 PM In reply to

    Re: Tips:Behavior of not() function

    Hmm, all of this depends how you use not function
    if you use it on a node then it works the way you have given. If a "not" is applied on a condition like "field1 = field2" then it will negate the result of "field1 = field2".

    If you use some other functions in then it works the same way as above. for ex:
    not(string(field1)), will give you "true" when field1 does not have any value in it and "false" when field1 has any value in it.
  • 10-23-2006 11:14 PM In reply to

    • hotikisu
    • Not Ranked
    • Joined on 10-20-2006
    • Japan
    • Posts 6

    Re: Tips:Behavior of not() function

    Thank you Agni Jonnalagadda.

    I understand that a result of a Boolean operation was reflected by an not() expression, example "field1 = field2".

    I think, we expect of not(string(field1)) function result "true" when fied value is "false", and expect "false" when field value is "true". But not(string(field1)) result "true" when only field1 value is blank.

    ----------------------------------
    field1 value / not(string(field1))
    ----------------------------------
    true / false
    false / false
    blank / true
    ----------------------------------

    If these are different as a result of you, it may be a bug of a Japanese version if it lends it. Or I may neglect the check that I must do something of.
    ---------------------------------------
    Yoshio Matsumoto (hotikisu)
    MVP for InfoPath, Japan
    ---------------------------------------
  • 10-24-2006 01:42 AM In reply to

    Re: Tips:Behavior of not() function

    These are the same cases I expect.
    I wasnt talking about giving boolean values in the field.
    I was more talking about a way we can achieve boolean results from not() also using not(field1 = "true").

    Thanks for the discussion here.
Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.