-
For the second button, just switch it to Action = Rules, and add a rule that closes the form.
-
I'm not sure what you mean by "expanded" - sorry! :(
-
My first guess would be XSN size. What's the file size of your XSN form template?
-
You will run into performance issues if your attachments are large, or if you have many files. Remember that the XML size will include the attachment's size. As to an exact size limit, it would depend on the environment/server.
-
I think that InfoPath creates the XSN form template it locks the schema to make sure that it stays in sync with the SharePoint list it's based on.
So in theory you would make changes to your list first, then the form would get "refreshed" (sorry, I'm not sure of the correct term) to match the updates made to the list.
What are ...
-
I'm pretty sure that button actions can only happen in either the InfoPath Filler or in the browser (if it is a browser enabled form). I don't believe that buttons can be clicked when the form is attached to an email view and sent via email. Sorry! Are you using SharePoint and would you consider switching to browser forms?
-
Hi,
Here's a good blog post from Microsoft. It's a good read and a good place to start!
http://blogs.msdn.com/b/infopath/archive/2010/04/22/comparing-list-and-form-library-forms.aspx
Good luck!
-
Indeed, the SharePoint calendar does not like the date/time format. Hilary has come up with a nifty workaround: using FormatDate to set the dates to "u" format, meaning that now they'll have Z at the end. SharePoint seems to like this format. Here's the command:
concat("FormatDate /date=", <datefieldhere>, " ...
-
We're investigating. More soon...
-
I wonder if it might be a formatting issue. The SharePoint calendar list might want the date/time to look like this (and perhaps InfoPath is not matching exactly the format):