"Some rules were not applied" warning displayed in InfoPath 2010 but OK in InfoPath 2007 - InfoPath Dev
in

InfoPath Dev

"Some rules were not applied" warning displayed in InfoPath 2010 but OK in InfoPath 2007

Last post 08-03-2014 10:40 PM by JenniferLindsay. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 07-28-2014 02:03 AM

    • chrvi
    • Not Ranked
    • Joined on 06-02-2014
    • Posts 3

    "Some rules were not applied" warning displayed in InfoPath 2010 but OK in InfoPath 2007

    Hi, I have a form which displays a "Some rules were not applied" warning message even if I open the form directly in InfoPath 2010 Filler but the very same form is opened with no such message in our customer's environment (they use InfoPath 2007).

    I'd like to get rid of this warning message in our environment but I have no idea why this happens only to us and the customer is able to open the form with no problem.

    Can this be caused by some difference between InfoPath 2007 and InfoPath 2010? Or is there some property which could be configured in InfoPath to ignore potential rule problems?

    Any hint/idea would be welcome...

    Thanks,

    Radek

    PS: The "Some rules were not applied" warning details: An error occurred in the form's rules or code. The number of rule actions or the number of calls to the OnAfterChange event for a single update in the data exceeded the maximum limit. The rules or code may be causing an infinite loop. To prevent this, ensure that the rule action or event handler does not update the data which causes the same rule action or event handler to execute.
  • 08-03-2014 10:40 PM In reply to

    Re: "Some rules were not applied" warning displayed in InfoPath 2010 but OK in InfoPath 2007

     It sounds like you have a set of rules that are executing indefinitely, over and over, when you open the form.  Do you have any Form Load rules or default value formulas? If so, check these very carefully and make sure you don't have a situation where Rule 1 on Field 1 updates Field 2, which then causes Rule 2 to run and update Field 1, which causes Rule 1 to run again...etc, etc.

    Jennifer Lindsay
    Qdabra® Software/InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™

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