-
Thanks - I'll take a look later today and post back. :)
-
I'm sorry, I should have been more clear - I meant if you are using InfoPath 2010 or InfoPath 2013. Do you know what version of InfoPath you are using?
-
Hello Zippy,
Overall I would say that it would be easier to have the entries as separate fields, because then you can promote them in SharePoint columns, and know whether the user entered the data or picked from a list. This would be especially important if the user entered data that was not an exact match to the course/course ...
-
Hello FSU_InfoPathUser,
Thank you for you inquiry. In order to check the entries individually in the repeating table, I would suggest requiring the data source using a query value. Each time a user enters a value in the repeating group, the query field of the 2DS should be set and then required. If the entry exists then an error ...
-
Hello Panthera,
Thank you for your post. In order to have a template part that displays on multiple SharePoint sites, the form must be published to each site you would like to have the web part on. If you have data connections to the site, they will also need to exist on the site unless the connections have been converted to a udcx. ...
-
Thank you for the speedy reply!
There is not any code in the form, we have modified the web service connection file to use an application id to connect to the web service. Similar to the UserGroup web service, we need to set the userLoginName to the current user into the form. As of now, the "Checked Out User" ...
-
Hi there,
How about sending a link to the form in your workflow emails? Then when your approvers click the link to open the form, you could show them a read-only view of the data so they could see but not modify it. Then you don't have to worry about passing data from one form to another.
If you really want the ...
-
-
-
Hi there, thanks for the reply. I'll try and explain in a different way..
I have an initial form that uses a repeating table (firewall form.png) for the details of a firewall rule. initially only one row, but could potentially be any reasonable number (2, 4, 9, 13). Then I have a SP2013 workflow for approval ...