InfoPath Dev

I am using InfoPath 2010 and SharePoint 2010.

I am creating a "Report" form which is pulling data from 2 SharePoint lists. 

The SharePoint lists are "master" "child"

I want to pull the data from the Child list and include some data from the Parent.

I have created a repeating table and in the repeating table I have some calculated fields which pull information from the parent based on the current() child.  All is well and this works fine.

When I come to publish this to the browser I have some "Control Binding is Unsupported" messages.  I have dug deeper and found that these messages are generated by the calculated fields which I want to have formatted as a date.

I have deleted the fields and re-calculated.  And I find that everything is ok with no error until I add that date formatting.  Once I have added the date formatting, even if I change it back to text I get the "control binding is unsupported".

The xml used in the calculated field is

xdXDocument:GetDOM("Request List")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:Order_x0020_Delivered_x0020_Date[../d:ID = current()/d:Request_x0020_ID]

Everything works great in local preview.

Is there any way I can have my "date fields" formatted as dates without getting this error ? 

Thanks in advance

Catharine

Hey, Catharine!

So, this is an ugly bug. The only fix I currently know works is to save the form as source files, and then, in the view, in a text editor, search for xd:xctname="ExpressionBox". When you find your expression box that is causing the error, find the xd:binding attribute in that span, and delete the attribute and its value.

Obviously, back up your form first, etc. :)

Thank you Hilary...

I have had a look in the view and this is one of the "offending" fields. Just want to confirm I have identified the correct deletion - I have highlighted in bold and strike through - is that correct ?

That looks correct.

One alternative solution to this problem that I have used sometimes is to create a new calculated value box, copy/paste the expression into it, and then delete the old one. That tends to work as well.