-
The taskpane is showing the source of the taskpane content instead of the content itself. To remedy this, please do the following:
Go to Tools->Options... in Internet Explorer
Click the Security tab
Make sure the Internet zone is selected and click the "Custom level..." button
Scroll down to "Open files based on content, ...
-
I believe you should be checking
if chec.text = "true"
-
"/my:KickOffRaum" can't possibly be the correct XPath for the node, unless your entire form has only one field in it.
If there is only one field called KickOffRaum in your form, then the XPath "//my:KickOffRaum" (note the two slashes) should work.
-
The most likely cause of the "Could not determine the database schema. Check your connection string and try again." error is that the query builder is unable to establish a connection to the web service, and not necessarily an internal error in Query Builder. This could be due to a number of possible reasons:
The web service ...
-
Unfortunately, the Qdabra Web Services cannot perform single queries on multiple databases.
Are both of your databases located on the same database server? If they are, I would think it would be a simple matter of creating a view (database view, not InfoPath view) to pull the data from both databases.
-
[quote user="Shiva"] Do you want to display by default 7 repeating sections? Then you have to add similar nodes in template.xml then you will get by default 7 repeated ections.
[/quote]
You can also modify the form's schema and change the minOccurs and maxOccurs attributes of the repeating node to 7, but either method ...
-
[quote user="bladah29"]The query cannot be run for the following DataObject: DescribeListSchema
InfoPath cannot run the specified query.
The SOAP message cannot be parsed.
[/quote]
Was there any more to this error above? I would have expected there would be more details. If there are, they could help us out quite a bit.
-
An XSN file is simply a CAB file with XML, XSD, and XSL files in it. If you use a CAB library to crack it open, you can inspect the schema and provide a list of the node names in it.
If you are going to be doing this with a lot of XSN files, may I direct your attention to Qdabra's InfoPath to XML Tool? It does typically require ...
-
I don't think it's possible to insert actual line breaks into an InfoPath textbox control, but they can be used in RichText controls, if that would be an acceptable option.
-
The xmlns:xsl attribute is not the problem. That's normal. In general, you cannot just take any XSL and use it in an InfoPath view.
I would think that the <label>, <input>, and <option> tags would make InfoPath upset. They are HTML elements but I don't think they can be used in InfoPath forms. ...