InfoPath Dev

Hi   Thanks for your help, I finally got there (very proud of myself!).    

The path might be correct, but the method name is not. Use XDocument.DOM.selectSingleNode instead of XDocument.DOM.selectingSingleNode.

Welcome. You may want to look at the free developer download of the Database Accelerator Web Services Suite. It has an Active Directory web service included.  It can also make creating secure, controlled, enterprise form solutions much easier by integrating with SQL. Qdabra Database Accelerator Suite Version 2.0 - Developer

Hello Michael, Thank you for sending me your solution, I have looked at it and the problem is indeed a schema issue: your schema is too complex for InfoPath Forms Server to handle correctly. I have created a simple repro of the problem by simply creating a new empty solution from your schema, dragging a few controls into the view and adding ...

Hi Guys, First of all, I wanted to thank all of InfopathDev.com team for providing such a excellent job in helping people like me. We are planning to deploy Infopath 2007 broswe based forms to Sharepoint 2007 and as per few blogs, I have to convert my web services which are consumed by my infopath form to UserConnectionData files(.udcx). What is ...

Uups, rollback. It seems to work if I use the same type of expressions which are used when InfoPath looks for digital signatures.  This works: xdXDocument:GetNamedNodeProperty(/ns3:A7140Message/baseMsg:MessageHeader/baseMsg:Fachlich, "AngeforderterStatus", "ENTWURF") = "ENTWURF" This works ...

It's a crazy thing! I just found out, that the "Conditional Formatting Expressions" which are added by InfoPath itself (when I used digital signatures and set the option "set fields read only after sign" = true) are working fine. When I try to use the same expression and and them manually to another field it makes boom. ...

Very interesting! My guess is that your schemas is what really causes the problem - although InfoPath has no problems with them, InfoPath Forms Server fails to process those schemas and therefore it fails whenever you start using xpaths on those. I would not be surprised if you also had problems with Rules and Calculations or Expression Boxes (let ...

Hello, I can share the solution, I just preparing it for you. I played a little bit around like you advised me and I found out that an expression of "1=1" works like a charme but as soon as I use some Xpath it makes boom.  I have a litte speciality which could be relevant. I have three schema files. BaseTypes which contains ...

If you cannot share out the entire solution try to see if you can simplify it while still getting the error - remove business logic, extra controls and aux-doms...  Or other approach is to create a very simple solution, add the conditional formatting that you have there and see if it crashes the Forms Server.