Search - InfoPath Dev Sign in | Join | Help InfoPath Dev InfoPath Dev is dedicated to bringing you the information and tools you need to be successful in your Microsoft Office InfoPath development projects. Home Blogs Forums Photos Downloads Search More Search Options Page 1 of 1 (5 items) Re: FormError properties fails in a browser-enabled form Hi Hilary, Still throws the same error for Site property, e.g. Site.Localname.ToString(). (Here I believe ToString() is required. I've excluded other properties while testing). And yes, the extra parenthesis was a typo. I've also removed the superfluous ToString(), which didn't seem to influence the outcome anyway. Without ... Posted to Code (Forum) by Alf Kiil on 11-01-2010 Re: FormError properties fails in a browser-enabled form Hi Hilary, I already checked that NrErr works (and by the way, it's just a counter value that is set for each new repeating group). The error occurs when I uncomment the first FormError property (Message). I've also tried without writing error data to a new errornode (i.e. I've taken out NewGroup) and instead written an ... Posted to Code (Forum) by Alf Kiil on 10-26-2010 FormError properties fails in a browser-enabled form Hi again. I've written code to populate a form errors list (to be displayed in an errors view when users trigger a button). It works great in client view, but fails in a browser-enabled form. After having spent a considerable time trying to solve this, I've concluded I'm in need of your considerable expertise. Tests indicate that the ... Posted to Code (Forum) by Alf Kiil on 10-26-2010 Re: How to traverse from an errors object to its parent node (using C#)? Hi guys, It works. By the way. In my particular case, I was looking for the top level nodes where the names of the nodes varies (i.e. they don't always start with "my:CompanyTable"). The solution that works for me is simply: string topNode = ... Posted to Code (Forum) by Alf Kiil on 09-29-2010 How to traverse from an errors object to its parent node (using C#)? I am trying to implement an “errors page” (a separate view) in InfoPath browser-enabled forms, because users often find it difficult to locate errors in multiple view and complex forms. An errors page may also facilitate more and better information/links to resources/guidance on errors than mouse over info allows for.I am extensively ... Posted to Code (Forum) by Alf Kiil on 09-23-2010 Page 1 of 1 (5 items) Copyright © 2003-2019 Qdabra Software. All rights reserved.View our Terms of Use.