You searched for the word(s): 12
-
-
Thanks for the reply. It appears to be a versioning issue. I'm having some luck changing the template version to a number higher than the forms version #'s. Then going into library settings into the SharePoint form library and relinking to the current library and matching the content type. I'm doing this on a test form library before ...
-
-
I think you hit it on the head. I am working with a list form rather than a "regular browser form".
I will explore switching my type of form. I used to do the local InfoPath forms and used repeating fields all the time.
When the browser forms came out, they told us the browser forms wouldn't support ...
-
Sounds like you may be using a SharePoint list with a customized form. If you need one to many relationships (sounds like you do!) you may want to use a library form instead. Create a new, blank InfoPath form from the Designer menu, and you'll see you can add repeating controls. Promote the fields you need to the library for your workflow.
-
You may not have published the template. Where do people open the form from? What types of issues are you seeing? You can attach screenshots under the options tab - either one where you've pasted all the errors, or you can add several posts with one screenshot per post (warning - if you post more than one time per minute, the SPAM filters will ...
-
-
Hi - so you just changed the data type of the field? It didn't get renamed or anything? Because the schema validation errors usually show up in the browser when we rename / move / delete a field. What are the versioning settings on the form template under Options > Versioning?
-
-