unwanted data validation - InfoPath Dev
in

InfoPath Dev

unwanted data validation

Last post 02-28-2008 10:57 AM by blackhawk. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 04-21-2006 08:54 AM

    unwanted data validation

    Hello,
    I am running into a problem with data validation. I have 2 fields that users have to enter latitude and longitude. The data type is "double, not required"(<xsd:element name="PHYS_LOC_begin_latitude" nillable="true" type="xsd:double"/>). I need this field to be validated but not required. I've used the "data validation" button and the field then becomes required. Is there a workaround for this? Can anyone help?
  • 04-21-2006 09:33 AM In reply to

    Re: unwanted data validation

    What about putting a default value in the field that you can than use in a rule to exclude validation if the default value is not changed?.
  • 04-21-2006 10:56 AM In reply to

    Re: unwanted data validation

    Any ideas on how that might be done? I've tried it with no success....
  • 04-21-2006 10:57 PM In reply to

    Re: unwanted data validation

    Add a rule that fires when the field is changed (this is the default, no condition rule). For this rule, add an action to set another value (ideally in a secondary data source). Use that value to conditionally enable or disable validation on the original field. Good luck Tracy!
    Patrick Halstead
    Project Manager at Qdabra
  • 02-28-2008 10:57 AM In reply to

    Re: unwanted data validation

    Why not just add to the data validation  AND Lattitude "is not blank" to whatever you already have?

Page 1 of 1 (5 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.