-
I think a list of users is easiest. I would have the column with the user information just be a person or group picker - then when you connect to the list from InfoPath, you can disable the button if none of the values in that list column match the current user (using the userName()) function).
-
Ah-hah, now I understand! The issue is actually due to the nature of a multi-select list box, unfortunately. So - you'll see that the Value field is repeating if you look at the schema in advanced view. Unfortunately, when we select and deselect options in a multi-select, behind the scenes, InfoPath is inserting and deleting instances of this ...
-
Ooooh, I'm confused. Can you attach a copy of your form under the Options tab in a reply? One thing - if you need to work around the five condition limit, change the first dropdown for your condition to "the expression" and you can copy out the actual XPath to the condition and add the "and" or "or" as appropriate ...
-
See attached sample form. Save the sample form locally. Right click and select design, then preview to try it.
-
To test existing XML, download locally, and then you can find under Form Options > Preview. I usually set versioning in the Form Options to not upgrade for this test as well, so if the schema changes involve anything that might cause a problem for existing data, I'll get an error when I preview. You can find more instructions here: ...
-
I would just delete the test records and make your current, tested site the live production site. The List IDs in the lists will not start at 1, since that field is an auto-incrementing int, but that ID field is mainly just used by SharePoint internally to identify what item you are looking at - you probably don't even have it showing in any ...
-
Well, whether the update will break existing XML depends on if you made certain changes to the schema. If you are not sure your changes will break existing files there are ways to test that - let me know & I can get you steps. Otherwise, you would need to switch your library to use content types. You could take the original (currently ...
-
Well - the button would just say "save" on it - it would use your submit data connection to submit the form to the library (which is what you want, right?) and then you can add a rule to close the form, which is what I was thinking you didn't like about the built in save button? Perhaps I misunderstood your question?
-
Sorry you haven't had a reply. I was hoping someone w/ direct experience would respond. I think we ended up using rich text for some clients to work around this - you may want to see if a rich text field wraps. Of course, then you have the question of what to do w/ existing forms - but you could probably add a rule to copy the text over on ...
-
If these are list forms, you will be a bit stuck. If they are library forms, you could open the template in design mode, use save as to save a copy, then republish to a network location. However, you'll also need to change the submit logic for the forms, and perhaps they have other SharePoint dependencies. For the existing XML, you can save ...