locked
InfoPath 2010 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 RRS feed

  • Question

  • Have a large form and have put set action commands greater than 16 into one rule and am trying to figure out how to understand what causes this condition and how to diagnose and fix it

    Thank you

    chuck

    Monday, October 8, 2012 9:02 PM

Answers

  • Hi Chuck,

    Yes, there is a 16 actions limitation for each rule without user interaction. This limitation is designed to avoid infinite loop.

    For example, if you have a rule on field1 to set the other 4 field’s value. Also, you have 4 rules run when those 4 field’s value changed. This will also exceed the limitation.

    This limitation only applies to calculated value and it will not have any problem for those actions like submit the form, query a data source.

    Please check if your actions exceed the limitation and do some modifications. For example, instead of use 4 rules run when 4 field’s value changed, we can add the 4 rules to a query button.

    Thanks & Regards,
    Emir Liu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact tnmff@microsoft.com


    Emir Liu

    TechNet Community Support

    • Marked as answer by Emir Liu Thursday, October 18, 2012 2:44 AM
    Tuesday, October 9, 2012 8:53 AM
  • Hi Chuck,

    The restriction is a rule cannot have more than 16 actions including its chain reaction per form.

    Instead of use set a field's action, we can use Default value to the field that you want to set its value using rules.

    http://blogs.msdn.com/b/infopath/archive/2006/05/17/best-practices-for-rules.aspx

    Thanks & Regards,
    Emir


    Emir Liu

    TechNet Community Support


    • Edited by Emir Liu Wednesday, October 10, 2012 10:04 AM
    • Marked as answer by Emir Liu Thursday, October 18, 2012 2:44 AM
    Wednesday, October 10, 2012 10:02 AM

All replies

  • Hi Chuck,

    Yes, there is a 16 actions limitation for each rule without user interaction. This limitation is designed to avoid infinite loop.

    For example, if you have a rule on field1 to set the other 4 field’s value. Also, you have 4 rules run when those 4 field’s value changed. This will also exceed the limitation.

    This limitation only applies to calculated value and it will not have any problem for those actions like submit the form, query a data source.

    Please check if your actions exceed the limitation and do some modifications. For example, instead of use 4 rules run when 4 field’s value changed, we can add the 4 rules to a query button.

    Thanks & Regards,
    Emir Liu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact tnmff@microsoft.com


    Emir Liu

    TechNet Community Support

    • Marked as answer by Emir Liu Thursday, October 18, 2012 2:44 AM
    Tuesday, October 9, 2012 8:53 AM
  • Thank you Emir.

    So how do you populate a complex form without exceeding the limit?

    In this case we have a complex form with several lookups that are attached to drop down lists.  As the user selects a value several text boxes are updated from this drop down selection.

    In this form there are multiple views.  So if I have a RULE and pick over 16 actions in the total form is that the limit or does each view have that limit?

    Also if you have a form that has a RULE that has 16 actions that is the limit per rule, or per view or per form?

    If this is the case how do you populate a form with a lot of columns from drop down lists?

    So if you have a lot of SET VALUES that go to the attached data source, do a look up extract the value and place it into the text box are you limited in this fashion?

    Do you know of any links that illustrate how to design around this with a complex form?

    Thank you again for the help.

    Chuck

    Tuesday, October 9, 2012 3:35 PM
  • Hi Chuck,

    The restriction is a rule cannot have more than 16 actions including its chain reaction per form.

    Instead of use set a field's action, we can use Default value to the field that you want to set its value using rules.

    http://blogs.msdn.com/b/infopath/archive/2006/05/17/best-practices-for-rules.aspx

    Thanks & Regards,
    Emir


    Emir Liu

    TechNet Community Support


    • Edited by Emir Liu Wednesday, October 10, 2012 10:04 AM
    • Marked as answer by Emir Liu Thursday, October 18, 2012 2:44 AM
    Wednesday, October 10, 2012 10:02 AM
  • Thank you
    Thursday, October 11, 2012 10:49 AM