-
I have not tried this myself but I would guess no.
When one switches to InfoPath 2010, you could still design InfoPath 2007 forms (to maintain compatability for users).
Does IP2013 offer the option to save a template as a 2010 template? That might be the way to go.
-
Hi-
There's nothing I can think of, out of the box, in InfoPath to achieve this.
You might be able to use conditional formatting to show/hide a certain number of rows, though. I'm attaching a sample, though crude, it might help guide you to a solution using conditional formatting.
Good luck!
-
Hi and welcome to the world of InfoPath.
We're discussing this same topic in another forum thread, so I'll direct you there. If the question/scenario is not the same, let us know.
http://www.infopathdev.com/forums/t/24976.aspx
-
Thanks. It is indeed a SharePoint list form, and it has undergone numerous customizations. The first thing that strikes me is that this form has five views.
Since the data is showing up correctly in the SharePoint list, then the problem is the form. The form is probably not displaying the data as it is expected. Maybe some fields are in a ...
-
Typically when working with a SharePoint list, one builds the list, then clicks Customize form in the SharePoint ribbon.
SharePoint then generates the "version 1" of your form, and opens it in design mode in InfoPath, and you can make changes to the view.
If you built this form from scratch, maybe we should check whether you ...
-
Sure, that seems straightforward. Here's a sample form. Hope it helps!
-
Hi-
This is a bit confusing. Are you saying the data shows up correctly in the SharePoint list column, but then does not show up correctly in the form?
Did you customize the form? Perhaps something done in the customization of the form has damaged the view (which means there data is there, but the view is not showing the data).
-
If you have a SQL DB, you can design your tables and then design a form based on those tables. Users then submit directly to SQL.
You can submit the forms to a SharePoint form library and control access via SharePoint permissions, but you'd still need to send that data to SQL (which would involve, perhaps, a web service).
Here's another ...
-
If the issue is happening on all machines, then you're probably on the right path by publishing the form to a new library, and seeing what happens there. If the form works, then perhaps the original form library can be safely deleted.
Especially if you're still in a test phase, then deleting and recreating isn't that bad an option.
-
Did you add these fields as columns on the SharePoint list, or did you add them directly to the form template?
Typically, for SharePoint list forms, you add the columns first to the list, then design the template to add them as needed to the view. (not the other way around)