Sandboxed vs. Admin Approved - Hilary Stoupa
in

InfoPath Dev

Hilary Stoupa

Sandboxed vs. Admin Approved

Just wanted to quickly post this link, which describes the differences between publishing sandboxed vs. admin approved solutions.

I hadn't realized that sandboxed forms can't use email submit connections!

From the MSDN page:

Publishing Form Templates as Sandboxed Solutions

Publishing a form with code as a sandboxed solution is no different from publishing any other form to a document library. Just use the publishing wizard as usual and your form will be uploaded to the server and will operate in the sandbox.

Note that there are certain restrictions to deploying your form as a sandboxed solution:

  • Must be an InfoPath 2010 form.

  • Must use C# or Visual Basic as the programming language.

  • Cannot submit to e-mail data connections.

  • Cannot have properties promoted for part-to-part connections.

  • Must not have any managed meta-data controls or data connections.

Comments

 

cryptics said:

Do you know what they mean by "Must not have any managed meta-data controls or data connections"?

April 16, 2012 11:13 AM
 

Hilary Stoupa said:

I don't! That just came up at a training today. I'm wondering if it has to do with the External Item Picker - I'm thinking a form with one of those may not be able to be sandboxed....

However, doing another search leads me to believe it may have to do with some original plans to allow IP to work w/ managed meta-data (termsets) that was not implemented.

April 26, 2012 2:57 PM

About Hilary Stoupa

I wandered into development after working as a business process analyst for a global manufacturing company. I create InfoPath solutions for our clients as well as work as a developer on company tools that extend InfoPath. I've also been instrumental in creating the InfoPath Master Class training provided by Qdabra.

Copyright © 2003-2014 Qdabra Software. All rights reserved.
View our Terms of Use.