Browser Forms

Re: Cannot open IP form in Browser because Control binding is not supported

Hilary Stoupa — Fri, 10 Aug 2012 17:23:23 GMT

This is a problem I've only seen in InfoPath 2010, and, in my opinion, is an InfoPath bug.

Re: Cannot open IP form in Browser because Control binding is not supported

jerryO — Fri, 10 Aug 2012 12:05:51 GMT

I removed all of the xd:bindings that were associated with ExpressionBox and I still had 21 errors left in the design checker. These remaining errors were linked to computed values that were copied and pasted to the different views in the form. (Same computed value ). I removed the 21 that were copied and published the form. This fixed the problem I had, I am now able to open the form in a browser. I am no longer getting the Error from qRules either,

Thanks a million for your help, I am going to add the comupted values back in a make sure everything is working OK!

Can you explain why the bindings were creating these errors and how they got there?

Re: Cannot open IP form in Browser because Control binding is not supported

ErnestoM — Thu, 09 Aug 2012 19:37:21 GMT

Hi-

I took a quick look and I see quite a few instances where the xd:binding needs to be removed. Did you go thru all of these and remove them all? There is going to be an xd:binding attribute for every Calculated value that refers to the LanguageSettings.

Re: Cannot open IP form in Browser because Control binding is not supported

jerryO — Thu, 09 Aug 2012 19:26:10 GMT

I tried your suffestion with the same results. I only had 1 view file named view1, I removed the binding attribute and published it to the site.

I zipped up the indivdual files and attached them.

Re: Cannot open IP form in Browser because Control binding is not supported

jerryO — Thu, 09 Aug 2012 18:59:07 GMT

I will try this in the AM. I cannot open a new form from the library at all now becuase of the error I mentioned. It displays ok from the IP designer but this is the error when clicking the add doc link in the lib.

Form template: https://........./teams/lean/tracker/Event/Forms/template.xsn
InfoPath cannot open the selected form because of an error in the form's code.
Could not load file or assembly 'Qdabra.Tools.RulesLibrary, Version=4.2.4575.29315, Culture=neutral, PublicKeyToken=0582df40855a0fba' or one of its dependencies. The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))

Please advise

Re: Cannot open IP form in Browser because Control binding is not supported

ErnestoM — Thu, 09 Aug 2012 17:42:53 GMT

Are you comfortable looking at the source files?

1. First I would save a backup of the XSN.

2. Then save the form as source files.

3. Look for the file that corresponds to your view.

4. Open it in a text editor.

5. Search for ExpressionBox - see whether there is an "xd:binding" attribute that has the complete XPath for the expression

6. Remove the xd:binding attribute and saved the view.

7. Right click on manifest.xsf and select Design.

8. The design checker errors should go away.

Want to give that a shot?

Another option is that perhaps the view file (step 3) is smaller in size and can be attached.

Re: Cannot open IP form in Browser because Control binding is not supported

jerryO — Thu, 09 Aug 2012 17:02:07 GMT

the max size is 128k my template is 188k and it cant be zipped any further

Re: Cannot open IP form in Browser because Control binding is not supported

ErnestoM — Thu, 09 Aug 2012 16:57:24 GMT

You can attach files via the Options tab when replying.

Re: Cannot open IP form in Browser because Control binding is not supported

jerryO — Thu, 09 Aug 2012 15:22:55 GMT

Hilary seemed to be having the same issue. Is there any way I could send my template in and have you look at it. The calculated value is using a 2DC to pull back the correct language to display a text box. The code below is for the Project Title calculated value. I have a 2DC to LanguageSettings.xml stored in the Assets Library of the site. The calculated value is xdXDocument:GetDOM("LanguageSettings")/LocalSettings/Labels/Label/LocalLabel/@Value[../../@Name = "Project Title" and ../@Code = xdXDocument:get-DOM()/my:myFields/my:ProjLanguage]

It is pulling the correct language based on a drop down box for language which is using the same 2DC to pull English, German..etc from the 2DC.

This was all working fine in a browser even though i had the design checker errors, the only thing that is differnt is I created a new Form Lib to submit too.

<?xml version="1.0" encoding="UTF-8"?>
<LocalSettings>
    <Languages>
        <Language Name="English" Code="ENG"/>
        <Language Name="German" Code="DE"/>
  <Language Name="French" Code="FRE"/>
  <Language Name="Chinese Simplified" Code="ZH"/>
    </Languages>
    <Labels>
        <Label Name="Project Title">
            <LocalLabel Code="ENG" Value="Project Title"/>
            <LocalLabel Code="DE" Value="Projektname"/>
   <LocalLabel Code="FRE" Value=""/>
   <LocalLabel Code="ZH" Value=""/>

Re: Cannot open IP form in Browser because Control binding is not supported

ErnestoM — Thu, 09 Aug 2012 14:09:21 GMT

One error I have commonly seen for Calculated values is this:

http://www.infopathdev.com/blogs/hilary/archive/2012/01/19/ipfs-design-checker-errors-amp-print-preview.aspx

Could this be happening to your form? I don't know what the errors in Design Checker point to, but it might be worth checking.

As far as the qRules reinjection, is this an issue that has come up only for this XSN?

Cannot open IP form in Browser because Control binding is not supported

jerryO — Thu, 09 Aug 2012 13:36:40 GMT

I have an infopath form that I have applied language localization too from the Matt Faus article.http://www.infopathdev.com/blogs/matt/archive/2006/02/02/Add-Language-Localization-to-a-Form.aspx. I have saved the language.xml files in the Assets Library in the site the form is being submitted too.

The form has been working fine in the browser for the past few weeks. The Forms Library that I was publishing the form too became corrupt so I had to create a new Forms Library. I submitted the same form to the new form library and updated the data connections. Previous to creating the new library, I would get an error when publishing the form indicating that there were errors, but I would choose Publish anyway and everything worked fine.

I am now not able to open the form in a browser. When publishing the form I am getting the error and choosing publish anyway. When the form is finished publishing, i get "The form template has been published to the server bit it can only be opened n the InfoPath FIller becuase it contains features that are not compatible with Web Browsers.

I have 41 errors in the Design Checker all pointing to what seems like the Calculated Values that are pulling the labels for the language. The value of one of those fields is:

xdXDocument:GetDOM("LanguageSettings")/LocalSettings/Labels/Label/LocalLabel/@Value[../../@Name = "Project Title" and ../@Code = xdXDocument:get-DOM()/my:myFields/my:ProjLanguage]

The calculated values are all working correctly in IP and they were all working correctly in browsers until I created the new form lib. Can anyone help?

I am using Office 365. I cannot attach the template becuase it is 187k, I can send the template to anyone that is willing to take a look at it.I have attached the xml being used to get the language labels.

I reinjected the form and I am now getting the follwing error when trying to create a new form:

Form template: https://>>>>>/teams/lean/tracker/Event/Forms/template.xsn
InfoPath cannot open the selected form because of an error in the form's code.
Could not load file or assembly 'Qdabra.Tools.RulesLibrary, Version=4.2.4575.29315, Culture=neutral, PublicKeyToken=0582df40855a0fba' or one of its dependencies. The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))