InfoPath Dev

I'm running into an issue where some of the expression boxes in a view can be edited and some can't. Looking at the xsl for this view, I found that some expression boxes had: xd:disableEditing=''yes'' added, where others didn't. Developing a test form resulted in this setting always being added. I have no clue why this setting is not available on ...

Patrick, Thanks for your reply. My issue was related to another thread I opened about namespaces. This is the solution I'm using currently: It seems that I've found a solution to my issue. Now is the time to verify whether what i've done is a good idea. Please comment.... I extracted the form files I opened myschema.xsd Then I changed this ...

It seems that I've found a solution to my issue. Now is the time to verify whether what i've done is a good idea. Please comment.... I extracted the form files I opened myschema.xsd Then I changed this (under the root element): <xsd:anyAttribute processContents=''lax'' ...

I'm wondering what problems might arise when I change the defined namespace to another? <xsd:anyAttribute processContents=''lax'' namespace=''http://www.w3.org/XML/1998/namespace''/> This would help me in resolving an issue I have with unknown attributes.

Dear all, An external application adds a namespace and some attributes to the xml (I cannot prevent this). Infopath can't open the form anymore after this has happened. Is there a way to declare the namespace + attributes in Infopath so that when the namespace + attributes are added, Infopath is still able to open the form? The error I'm getting ...