-
So - are you also using a 2010 form with logic to submit to a list? Works in preview, returns the same error in the browser?
-
Wow - I have literally NEVER seen this before! I can see in the screenshots that both are displaying the same form view. Are all the machines w/ the issue using the same language settings?
-
I think you may need to add a SQL view for this, and a secondary data connection. With a SQL view, you could have a column with just the date value - and then use that for your filter. Or, perhaps you can add another column to your table with that information?
-
Is this a repeating data source? If so, see attached sample for a suggestion. Save the attached form locally, right click and select design, then preview. You'll note my "Complete" field is a text field so it can have a default value. If you need your "Complete" field to be Boolean, you could use a helper field with ...
-
Awesome news! Glad you got it. If you aren't already using Notepad ++ (free) with the XML plugin, I recommend it. You can click on an element in XML and get the XPath, as well as test expressions. Obviously, the XML may have namespace prefix differences in your InfoPath data connection, but it is a good tool for some quick testing of whatever ...
-
My guess would be something is different in the browser - not sure what tho. So you'll want to put TASKA on the form again, set to display the actual XML value in a text box. Same w/ the helper field - that may help you see the difference.
-
You should consider changing the datatype of the datepicker field to date - then regardless of the format, the XML will have yyyy-MM-dd
-
Well, sadly, InfoPath is not going to let you submit to both a list and library out of the box. There are some really good threads on here about leveraging CAML to submit to a list (which is the only no-code way to submit a non-list form to a list) - so if you aren't using Office 365 you may want to check that out.
Otherwise, you could ...
-
I'd drag that data connection onto the form & preview to see what the error returned is. Or run Fiddler when you create the data connection.
-
Seems like it should work - the original field is a date datatype?