Browser Forms

Re: Design Checker Error /Control Binding Is Not Supported

Kathy Street — Tue, 10 May 2016 17:42:43 GMT

I am new to InfoPath, I have a employee form and a repeating table from a document library showing the forms that each employee has on file. It only shows the ID of the document library document type and not the value of the document type; Application, I-9, W-4, etc. I tried changing the document type field to a calculated field and getting the value from the list that contains the document types. However, I get this error when I try to save. How do I save my form to source? And then remove the binding statement? any help would be greatly appreciated.

Re: Design Checker Error /Control Binding Is Not Supported

Peter B — Thu, 13 Jun 2013 07:08:17 GMT

Thanks. I fear with many things InfoPath, it may not be fixed if MS isn't going to commit to a suitable Enterprise Forms strategy, that supports an offline component.

Re: Design Checker Error /Control Binding Is Not Supported

Hilary Stoupa — Thu, 06 Jun 2013 14:07:41 GMT

I've not yet figured out a pattern - it is annoying, and I don't usually even bother with recreating the calc'd value, I go straight to the view xsl and delete the bindings, as unpleasant as it is.

Re: Design Checker Error /Control Binding Is Not Supported

Peter B — Thu, 06 Jun 2013 06:07:06 GMT

This is particularly annoying bug and is still present in InfoPath 2013. Trying the suggestion to re-create the Calculated Value didn't work. I had to hack the View XSL and delete the bindings. How does this error occur?

Re: Design Checker Error /Control Binding Is Not Supported

ErnestoM — Fri, 31 Aug 2012 12:31:56 GMT

The problem is this here:

xd:binding="xdXDocument:GetDOM("Approval Matrix")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:Who[xdXDocument:get-DOM()/my:PayPressureForm/my:Approvals/my:A_PopulationScope = ../d:Title and xdXDocument:get-DOM()/my:PayPressureForm/my:Approvals/my:A_JobGroup = ../d:Job_x0020_Group and xdXDocument:get-DOM()/my:PayPressureForm/my:Approvals/my:A_PayPressureType = ../d:Pay_x0020_Pressure_x0020_Type and xdXDocument:get-DOM()/my:PayPressureForm/my:Approvals/my:A_Period = ../d:Period and xdXDocument:get-DOM()/my:PayPressureForm/my:Approvals/my:A_PBSPercentage = ../d:Percentage]"

This should be a couple of lines below the snippet you have pasted, which is where the Calculated Value will get it's value.

But the xd:binding is what's causing the problem.

Re: Design Checker Error /Control Binding Is Not Supported

Olgierd — Thu, 30 Aug 2012 13:50:55 GMT

I found following line after extracting the source files:

Should I remove the whole line? How them I able to put the source files into one xsn file?

Re: Design Checker Error /Control Binding Is Not Supported

Hilary Stoupa — Wed, 22 Aug 2012 17:35:57 GMT

I've actually only seen this error in IP 2010.

So, under File / Publish, you can export source files.

Once you've done that, you can open the view file up in a text editor. From there, search for your calculated value. You may want to add some text or something before the control to make it easier to find - I use "FindMe" a lot, then search for that - view files can be pretty long.

You should see an xd:binding attribute that is causing the issue.

Re: Design Checker Error /Control Binding Is Not Supported

Olgierd — Wed, 22 Aug 2012 17:31:13 GMT

infoPath 2010

Re: Design Checker Error /Control Binding Is Not Supported

ErnestoM — Wed, 22 Aug 2012 11:59:24 GMT

Which version of InfoPath is this? Steps will vary...

The steps require extracting the template into its resource files, and looking at the manifest, so save a backup of your form before you begin.

Re: Design Checker Error /Control Binding Is Not Supported

Olgierd — Wed, 22 Aug 2012 10:15:27 GMT

Could you explain to a rookie like me what would need to be done (looking at the resolution provided which I dont understand):

"So, I saved the form as source files and took a look at the view - searching for ExpressionBox took me to one of the culprits. There was an "xd:binding" attribute that had the complete XPath for the expression - it was easy to see that the xsl:value-of node would be providing the actual value. Other expression box controls did not have this attribute, so I removed it and saved the view. When I opened the manifest.xsf in design mode, my design checker errors went away, and Print Preview started working as anticipated."

Re: Design Checker Error /Control Binding Is Not Supported

ErnestoM — Mon, 20 Aug 2012 13:07:52 GMT

This might be a common InfoPath error - I say that because it came up last week on another forum thread, and it happened to me a few weeks before that, and we have a blog post on it:

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

Hope this helps!

Design Checker Error /Control Binding Is Not Supported

Olgierd — Mon, 20 Aug 2012 10:53:25 GMT

Hi,

For the purpose of my webform I have loaded a big table into SharePoint as a list that is utilised as a approval matrix (5 drop downs show the end result - so appropriate level of approval required). I have created 5 drop down lists (where I filter out results, question 2, filters results chosen in filter 1 etc.) I have placed Calculated Value control to show the end result automatically so who needs to approve this request. When tryingo to publish a a webform I am getting a error message"Control Binding Is Not Supported (Binding a non-repeating control to a repeating field or group is not supported in Web browser forms. To fix this problem, remove the control or replace it with a repeating control, such a repeating section or a table". When I double click on the field it goes to my secondary field (Who) that is supposed to show the end result of filtering.

Who[A_PopulationScope = Title and A_JobGroup = Job_x0020_Group and A_PayPressureType = Pay_x0020_Pressure_x0020_Type and A_Period = Period and A_PBSPercentage = Percentage]