Logic inspector detects errors for field that no longer exists - how do I fix this? - InfoPath Dev
in

InfoPath Dev

Logic inspector detects errors for field that no longer exists - how do I fix this?

Last post 06-15-2014 05:11 AM by AmsterdamSchool. 0 replies.
Page 1 of 1 (1 items)
Sort Posts: Previous Next
  • 06-15-2014 05:11 AM

    Logic inspector detects errors for field that no longer exists - how do I fix this?

    My form started to display strange behavior. A rule checked a certain field for being empty. This rule worked as predicted. Letting the same rule test a different field (both simple text fields) it no longer worked. All I changed was the field it looked at in the condition. After a few hours of testing and tweaking I could only conclude that there the file might be corrupt. In the logic inspector I found a message about another field with a calculated value which was referencing other fields that didn't exist. The problem is that the calculated field that had these issues also no longer exists. So the bottom line is that the inspector sees an error in a non existent field... Could this be causing my issues? The fields are not related, but maybe this caused the file to become unstable? Are there any possible fixes or things I could try? Thank you
Page 1 of 1 (1 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.