-
Sorry your posts got caught in the moderation queue. The basic steps to run your code in debug should work no matter which version of InfoPath you are using - mark a break point in the code and start from the code editor instead of from preview. The XPath you pasted - //COMPANY[@SELECTDELETE] - appears to be invalid? You don't have a ...
-
This is completely possible - does your data for your dropdowns come from secondary data connections, like SharePoint lists? Or do you currently have the options typed into the drop down properties?
-
If this is a browser form, you can add a calculated value to your form with the message you wish to display and use conditional formatting for displaying it. If this is not a browser form, you could add a rule to each of these fields to display a message box popup if both are not blank, based on the value. See the attached sample - save the file ...
-
Sure, you can use code for this. I'd suggest unless you are a VB.NET programmer that you use C# instead, since you will find more samples in C#. If your form is browser, Office 365, you won't be able to use code.
-
There isn't any out of the box way to do this. But you may be able to leverage Excel services if this is not a browser Office 365 form & you have Excel services available on your SharePoint server.
-
Hi, Nate - sorry, not to my knowledge. It would be a nice feature & I know I've seen people ask about it before it, but there is nothing built in to InfoPath that would do this. In theory, I wonder if it would be possible to add jQuery to a browser form to add autocomplete, but I've never tried that. :)
-
The general approach should be the same, regardless of the names of your fields. Attach your form file under the Options tab if you need a hand. :)
-
I should add, if you have a lot of forms you need to change, you could always copy them locally and use PowerShell to replace the href (or another tool of your choice) with the correct one, and then copy them back into the library.
-
I'm so sorry - I just tested this and you are right - relink did NOT set the form to the default content type! However, in my test form library, I was able to change the content type under the file's properties in SharePoint - see attached screenshot.
-
Your rules are really.... odd. I don't understand them at all. Rules shouldn't be set on the field they target. Why not just put both rules on the Update field? So when it changes, it sets the date and the user? Or, see attached for an approach that uses rules on the repeating section itself. If you want to use defaults, you should be able ...