-
Well, you can right click the text control and select Change Control and change it to a drop down - but then ALL your CAML fields will be drop downs and you'll have to do something tricky to only get the options you want to display in each one. Probably easier to use form fields and then set your CAML values. You can modify the manifest file ...
-
I'm not sure what you can with an existing list - but if you create a new list starting with the SharePoint List template in InfoPath, you have an option to manage multiple list items with a single form....
-
Your node variable should be an XPathNavigator in InfoPath - here's an MSDN link. https://msdn.microsoft.com/en-us/library/bb509311(v=office.12).aspx - it says it is for IP 2007, but 2010 and 2013 use very similar concepts.
-
I'm sorry - I'm not sure what could be causing this. I sometimes also get a memory error from IP - usually when I have a few forms open in design mode & also one I'm filling out or something.
-
Well - if you created an InfoPath 2013 form and are trying to open it with an earlier version of InfoPath, you'd get this... but it sounds like you created the form with InfoPath 2013 and are opening it in InfoPath 2013... You can always open the form in design mode again and change the compatibility under File > Form Options > ...
-
What if you go to the form templates library where the content type is - can you open it directly from there? Sorry, I really don't know what is going wrong, just figured it would be worth a try. I'm guessing template.xsn is NOT the content type you actually want. "Form" isn't set as the default content type for the library, ...
-
Generally I have a dev or test site so I can verify my changes and test. I would not be comfortable publishing anything but the most minor change to production without first testing the published forms, since browser forms can behave in unexpected ways. I publish the updated template to production either during a previously determined ...
-
I mention it here: http://www.infopathdev.com/blogs/hilary/archive/2015/10/26/office-365-amp-infopath-browser-form-limitations.aspx
We also had a webinar where we talked about it. The issue is with the Sandbox in Office 365. We've seen qRules (and forms with code) slow to load in the browser, and we've seen users get ...
-
Well - the rule on field B should set field A to blank. Then add a conditional formatting rule on field A to highlight it if it is blank.
-
Depends on how you want your form to look. For now, why not just try a repeating section with controls.