Infopath Processing Error

(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  HomeLearnDownloadsCommunity Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Infopath 2010 form. When I invoke the Rule Inspector on a field, under the ACTIONS section, I see 'Processing Error'. SharePoint > SharePoint 2010 - Using SharePoint Designer, InfoPath and Other Customizations Question 0 Sign in to vote I have a complex Infopath 2010 form. It has many rules, but no code. When I invoke the Rule Inspector on a field, under the ACTIONS section, I see 'Processing Error'. Is there anything I can do to troubleshoot this error? George W Moved by Hemendra AgrawalModerator Tuesday, August 05, 2014 10:38 AM SP 2010 Friday, August 01, 2014 6:45 PM Reply | Quote Answers 0 Sign in to vote Hello George , I am not able to reproduce this issue but It seems you have invalid rule in form buttons. Could you please verify all button rules and also check the submit options in data tab.Hemendra:Yesterday is just a memory,Tomorrow we may never see Please remember to mark the replies as answers if they help and unmark them if they provide no help Marked as answer by Victoria XiaMicrosoft contingent staff, Moderator Sunday, August 17, 2014 11:43 AM Tuesday, August 05, 2014 10:37 AM Reply | Quote Moderator All replies 0 Sign in to vote Hello George , I am not able to reproduce this issue but It seems you have invalid rule in form buttons. Could you please verify all button rules and also check the submit options in data tab.Hemendra:Yesterday is just a memory,Tomorrow we may never see Please remember to mark the replies as answers if they help and unmark them if they provide no help Marked as answer by Victoria XiaMicros

up in your InfoPath form by using the Logic Inspector to find unused business logic. ADVERTISEMENTS An InfoPath form template consists of two core parts: A Main data source. One or more Views. View vs. Main data source The Main data source is the heart of an InfoPath form template, while a View is a window into part of that heart. By default, when you add a control from the Controls task pane to a View, InfoPath automatically creates a field for you in the Main data source of the form template. On the other hand, if you delete a https://social.msdn.microsoft.com/Forums/windowsserver/en-US/97788d12-888b-4456-9749-9ca5abe6982c/infopath-2010-form-when-i-invoke-the-rule-inspector-on-a-field-under-the-actions-section-i-see?forum=sharepointcustomizationprevious control from a View, InfoPath will not remove the corresponding field from the Main data source. The field will exist until you manually delete it yourself by going to the Data Source task pane. This is an important fact to remember when you start getting validation errors popping up or other strange things happening in your form template. Such errors may be related to controls and corresponding business http://www.bizsupportonline.net/blog/2009/quick-tip-finding-hidden-errors-infopath-form-template.htm rules (data validation, default values, rules, and code) you thought you had deleted, but in fact, still exist in your InfoPath form template. Golden Tip: To permanently delete a field from an InfoPath form template, delete it from the Main data source. You can prevent InfoPath from automatically creating fields in the Main data source of the form template by deselecting the Automatically create data source check box, which is available at the bottom of the Controls task pane. How to find sources of errors in an InfoPath form template A quick way to find out whether there are rules, data validation rules, calculated default values, or code present within an InfoPath form template is by using the Logic Inspector. The Logic Inspector is especially handy if you have large and complex InfoPath forms with many controls and business logic. It also helps you find unused fields and business rules, which you may have added at one point in time, but which are not required anymore in your InfoPath form template. It is important to remove such unused fields and business rules, since they might cause problems and/or interfere with the proper functioning of your InfoPath form later on. You can a

for InfoPath 2007, 2010 and 2013. You can read articles, tips, and tutorials. It has code samples and complete applications as http://blog.walisystemsinc.com/2007/12/inspecting-logic-and-checking-design-of.html well. A Practical Guide to SharePoint 2013 A Practical Guide to SharePoint http://sharepoint.stackexchange.com/questions/30980/default-values-rules-or-code-may-be-running-in-an-infinite-loop-infopath-2010 2013 - Book by Saifullah Shafiq Wednesday, December 26, 2007 Inspecting Logic and Checking Design of InfoPath Form Inspecting Logic and Checking Design of InfoPath Form It is easier to inspect the logic manually in simple forms but companies use InfoPath not to create simple forms but infopath processing to create forms in an easy and simple way. These forms can get quite complex and large. Once developed and deployed, there are different techniques that developers can use to track down errors but even at design time inspecting and fixing errors in the form can be a tedious job. Forms can have hundreds of nodes or may be 20-30 infopath processing error fields in a single view. It's not easy to find problems with the data sources without the help of a tool. Unfortunately, logic inspector and design checker, tools that come with InfoPath are usually overlooked and not taken advantage of by the developers. Figure 1: Logic Selector can be selected from the Tools menu There are some errors that become evident only after when a developer tries to deploy the form. Large number of data sources or fields is not the only problem, no form is complete without the data validation checks, rules and business logic. Logic Inspector enables developers to find problems with the form before they try and deploy it on the destination server. It allows them to view the data validation checks, rules, calculated default values, and business logic, all in one place. Design Checker is another tool that can be used to check the form design for performance related issues before deploying the form. I admit, even I used to underestimate the power of this tool but It really helped me once

for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us SharePoint Questions Tags Users Badges Unanswered Ask Question _ SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Default values, rules or code may be running in an Infinite loop - InfoPath 2010 up vote 3 down vote favorite 2 I am using InfoPath 2010. In the browser enabled form, i have a repeating table and have some rules set. When the number of rows inserted is more than 13, i am getting the below error: "Default values, rules or code may be running in an Infinite loop. To prevent this, ensure that the default value, rule action or event handler does not update the data which causes the same rule action or event handler to execute". In the 14 root log, i am getting the below: 03/07/2012 12:50:52.15 w3wp.exe (0x277C) 0x2C98 InfoPath Forms Services Runtime - Business Logic 82lj Critical Calculations exceeded the maximum stack depth. Further analysis on the form: I have a column, which has the default value set like this: count(preceding-sibling::*) + 1 This column is causing the issue. I removed the calculation on the column and the form loaded properly. However, this calculation is required. The column is used to find the right row index before setting a value from a lookup to the appropriate row. How to change this calculation? How to fix this error? Thank you infopath share|improve this question edited Mar 7 '12 at 12:49 asked Mar 7 '12 at 6:40 venkatzeus 417 Hi. There absolutely MUST be some other calculation or assignment to cause this issue. I have quite complex forms relying on this calculation and no issues with 50 rows in a repeating table. Dig deeper, use Rule Inspector and XML representation to analyze the logic. It may take some time, but eventually you will find it. –Alexey Krasheninnikov Sep 5 '12 at 7:44 OK, I could have been wrong. See answer bel