Error in rules: Fields are changing to XPath Expressions by themselves. - InfoPath Dev
in

InfoPath Dev

Error in rules: Fields are changing to XPath Expressions by themselves.

Last post 03-11-2013 07:33 AM by skivaly21. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 03-06-2013 08:37 AM

    Error in rules: Fields are changing to XPath Expressions by themselves.

    Hello all, 

    I have quite a big InfoPath file, at least 45 views so far...which will soon be over 90.  Our testers keep saying that a random button or section isn't working properly even when they worked fine the day before.  When I look at the rule that I've set, I can see that it has changed by itself.  The field in the rule will have changed to "The expression" with XPath to follow.  I'm guessing that it changes when working on, saving or publishing the file.  I wounldn't mind except for the fact that it will stop the rule from working and I have to change it back to a field.  I've included two screen shots to show the "before and after"to better explain my problem.  

     Thanks for any ideas!

     -Nick

     

     

  • 03-09-2013 01:25 PM In reply to

    Re: Error in rules: Fields are changing to XPath Expressions by themselves.

    Hi Nick,

    First off, I would caution you from creating such a big "kitchen sink" form. You should consider breaking it up into separate forms that communicate with each other. That will reduce load time and make it easier to maintain down the road.

    To answer your question, two things I can think of...

    1. typically, the rule will change to "The expresion..." when the data source changes. For example, you delete the field or rename it. Rename should result in the rule automatically updating the rule condition to the new field name but if your form has too many rules and an error in one of them, the rule parser may stop with the update.
    2. check for rule errors - go to Rule Inspector and scroll through looking for red text. If there is an error, please fix it. The rule parser may fail because of these. You can also export your form as source files (file->publish->export as source files) and open up the manifest.xsf and scroll through the RuleSets section. Sometimes, updating this to be correct (and then saving, and right clicking the manifest.xsf to reopen in the Designer) is the fail-safe approach, but be careful - it is a sharp knife and you should make backups.

    Good luck with all of the dishes piled high in the kitchen sink....

    :)

    Patrick Halstead
    Project Manager at Qdabra
  • 03-11-2013 07:33 AM In reply to

    Re: Error in rules: Fields are changing to XPath Expressions by themselves.

    Hi Patrick,

    Thanks you, It looks like I was moving a few fields to new folders AFTER I had already created the rules.  I'll move all my fields before creating rules from now on. 

     Is there an easy way to break up this form as you suggest? This is an area that I've never experimented before. It is unbelieveable how many rules are dependend on different parts of this form.  I'm already starting to receive "postback limit reached" and "exceeded amount of allowable resources".  Could these be solved by breaking up the form?  I'd like to keep these dishes clean and organized.

    Thanks

     

     

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