Hi there, anyone can give me his/her two cents?
Problem)
We have several complex InfoPath forms in production. Got a new requirement for one of them: Client needs to be able to upload large files to SP libraries using this IP form (as file attachments).
Caveat)
Although it is technically possible (incrementing user session data
-to allow large files- and moving programmatically the attachment to a
SP library -to don't blow up the form-), it seems like it is not
recommended because of the performance impact on the farm [1].
Looking for solutions)
Thus, we are thinking about how can we manage this situation
(leveraging the already designed InfoPath form). We have thought about several alternatives:
1) "Embedding" a FileUpload ASP.NET control within the form.
2) Simply put a link pointing to an ASP.NET page containing the FileUpload control.
Problems with the solutions)
1) I think it's not technically possible to upload files from
InfoPath without using the user/form session storage (even if it were
possible to embed the FileUpload control within the form).
2) Since we want to know if the user has uploaded a file -and, in
that case, which file it was- (to insert the proper reference inside the
form), we would need some kind of "feedback" coming back from the
ASP.NET page to the form. [It would be like a synchronous call, waiting
for the task to be done ... and then informing about the results of it].
I have been reading/thinking
for a while ... and wasn't able to come with a feasible solution (I
mean, any other than reimplementing the whole form from scratch without
using InfoPath technology).
Thank you very much in advance!!
[1] http://blogs.msdn.com/b/jorman/archive/2011/10/18/performance-impact-of-file-attachments-in-infopath-forms.aspx