IPFS, Design Checker Errors & Print Preview - Hilary Stoupa

InfoPath Dev

Hilary Stoupa

IPFS, Design Checker Errors & Print Preview

I don't know about you, but I sometimes ignore the Design Checker in InfoPath - especially when it is throwing an error over some poor expression box (calculated value) that it thinks is bound to a repeating group (what's that about any way? Aren't these things not bound to anything? Isn't that the point?).

Clicking on one of the errors above in my form popped up this dialog:

The text of the error is:
Control binding is not supported

And the message text is:
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 as repeating section or table. 

And one of my calculated values was selected. The cacluated value was displaying data from a repeating node in a secondary data source, but the XPath had a filter on it - only one value was going to be returned.

The form could be admin approved, and opened and ran in the browser without error.

But then, I added a print view to the form. Clicking the Print Preview button in IPFS would not switch to my print view if there were any design checker errors on the view that used the print view.

Gee. I could add a bunch more fields to my main data source to hold the "display" values for all the fields that I needed to be able to show info from my 2DS in this view. That seemed like a horrid idea.

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.

As always, before you save your form as source files and start poking around in them, make sure you have a backup copy.



Olgierd said:


I have encountered the same issue, but I am not a Programmer, so don't know what would be the easiest way to approach the problem? What did you do again?

August 21, 2012 6:33 AM

Paul G said:


Did you resolve this without going into code, I'm gettng the same error when adding a calcuated fields associated to a secondary data source. I've tried using it with and with out a repeating section, it works fine for a while then will suddenly return the error, but not only on the latest calculated field added but all the others.

Any ideas or pointers would be great.



September 4, 2012 1:06 AM

Hilary Stoupa said:

Well, my resolution doesn't involve code, but it does involve working with the source files. I don't know of a way to solve this in the UI.

September 5, 2012 8:20 AM

Mel Balsamo said:

Got calculated values on your InfoPath browser form? Do they involve filters and/or complex formulas

January 14, 2013 4:05 AM

Mel Clemente said:

January 14, 2013 4:07 AM

Peter B said:

Deleting the calculated value and adding a fresh one didn't work for me.

Man I hate InfoPath sometimes.

June 5, 2013 10:58 PM

Ed Boon said:

it is a solution but it's time consuming.

Grrr. Anyone have a better solution.

February 20, 2014 3:20 AM

Josue T said:

Well, it took me a few seconds, I did a quick replace for all xd:binding to _xdBinding.

You can go replacing one by one checking first that is a span element with xd:xctname="ExpressionBox" if you wish.

February 18, 2016 6:12 PM

Lucia said:

Thank you Hilary! You are great!!!

March 23, 2016 9:14 AM

Tilly said:

I have successfully deleted the xd:binding sections of the offending fields, but now each row shows the data for the first row in the lookup fields, the non-lookup fields are showing the correct fields.  

Have I missed something?

April 11, 2016 7:49 AM

Hilary Stoupa said:

Hi, Tilly - I haven't had this happen. Did you save a copy of your form prior to trying this? Maybe email me via the forum & I'll reply so you can send me the template & I'll take a quick look at it.

April 11, 2016 7:55 AM

About Hilary Stoupa

I wandered into development after working as a business process analyst for a global manufacturing company. I create InfoPath solutions for our clients as well as work as a developer on company tools that extend InfoPath. I've also been instrumental in creating the InfoPath Master Class training provided by Qdabra.

Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.