-
Will this list change frequently? If so, I'd use SharePoint. If not, I'd use an XML file in my InfoPath form. :)
-
Hi, Erik - I went ahead and moved this to General since I don't think you'll need code here. :)
You will have the user's name from the userName() function in InfoPath - is that adequate for what you need to do? What do you need to compare to in order to determine who can review a form?
-
Maybe this will help? https://www.spjeff.com/2012/12/10/infopath-2013-missing-programmability-components-fixed/
-
Hi - you can submit data to Access from InfoPath, but submit is disabled in browser forms. This is limitation in browser forms, unfortunately. This screenshot is from documentation for an older version, but still holds true. ...
-
I think the issue is just that your site template is 2010 and Office 365 is 2013 or maybe even 2016 by now. Maybe instead of using a site template, save each list and library as a template?
-
Oh how frustrating. My guess would be that if the ID isn't getting correctly generated that you are having overwrites. And you are doing this on submit, so it does seems like you should be getting this number correctly (sometimes people do this sort of thing on form load, so you can see how that might cause an accidental case where ...
-
You will definitely have to use code for this (or try qRules) - I think the easiest approach would be to have an XML file data connection to a single form in the Project Description library, and when the user selects a project, change that data connection to point to the correct file, then execute the query. That gets you back your repeating ...
-
I may have been unclear. I don't know of anything in an IP 2007 form that will not work correctly in SharePoint 2013.
There are features available in InfoPath 2010 / 2013 that are NOT available in InfoPath 2007 designer. The only reason to upgrade your form would be if you want some of these new features.
-
You aren't a dunce at all - this stuff is confusing. Glad you have it working. :)
-
Well, usually that just means that there is something wrong w/ the structure - like the fields belong inside a repeating group and you've put them outside of it. :) Try copying the entire view from one to the other, then remove the fields you don't need, see if that helps. Feel free to attach your form under the Options tab in a ...