InfoPath Dev

Hi All,

We have recently migrated from SharePoint 2007 to SharePoint 2010. We did not do an inplace upgrade or db attach upgrade, we used a 3rd party Migration tool to move all the content from one server to another. This was because we completely reorganised our site collections and sites. All infopath forms worked fine after tweaking the data connections bar one, this form happens to be an Administrator Approved with managed code to populate various controls and this form is giving problems with the attachments. When we try to open any forms with attachments the form opens fine, however when we try to open the attachment we get a 'file not found' error. This also happens if I add a new form to the library and add an attachment. Any ideas on how to resolve this would be welcome.

Thanks,

C.

Questions:

1. Were the attachments links or actual file attachments?
2. Are you opening the InfoPath form in the rich client (filler) or a browser form?
3. If you open the form in the filler and save the XML to a local directory, can you open in Notepad and see the Base64 encoded attachment?
4. Why is the form admin approved? Is it because there's code in the form? Have you looked at the code to see what it does?
5. Have you tried publishing as a sandbox form?

Hi Patrick,

1. The attachments are file attachments.

2. I'm opening the form as a browser form.

3. I have opened the form in filler and viewed the encoded attachment. I was also able to open the attachment in filler. However all users only have access to the browser form as they don't have infopath installed locally so I still need the attachments working in the browser form.

4. The form is admin approved because there is managed code that populates a drop-down list based on values selected in another drop down list. I was not the original developer of this form so I just inherited it and have had to maintain it.

5. I havent tried publishing as a sandbox form. TBH I dident know I could.

bumping in the hope of an answer.

This is not an answer, but I am experiencing the same challenge.  The file attachment control works in the form filler and as a published form as long as it doesn't have to be published as an admin approved form.  Once it is approved as an admin approved form, then the file attachment control works for attaching a file, but displays a file not found message when attempting to download the file ... from all except one site collection.  I did some experimenting and these are my results.

SharePoint 2010 MOSS and InfoPath 2010.

Through the activation process in the Central Admin ... when I select the Web Application (sharepoint:80) and the base site collection (/), then the file attachment control is fully functional.  If I run it in a different site collection within the same application (/Sites/Site1, /Sites/Site2, .etc..) then the download functionality of the file attachment control presents the file not found message.  This created another problem. If the form library where the file was being saved is in a different site collection or subsite than where the form was activated at, then the form library gave me the message that it was no longer web browser enabled.  So the "form library" also had to be moved to the first site collection (/) or the files would fail to open back up in the web browser.  Not sure why it only works in the original or first site collection (/) for an "Admin Approved" form, but these are results of my testing. 

There is news about a service pack for SharePoint 2010 to be released. http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=973

First of all, I would like to apologize for not seeing the reply in March.

Secondly, I would like to thank Prophet for the very interesting post and recommendation to install the SP.

I'm not sure why SharePoint 2010 browser forms do not read/display attachment fields saved in 2007 but it could have something to do with the object model change and the fact that the forms use code. That doesn't make a lot of sense, and is just the only wild guess I have ...

One possible workaround (if the Service Pack doesn't fix it) is to convert the attachments into links to files stored in a document library. This can be done in a batch way and would result in the added advantage that users can edit the attachments without having to open the forms (or maybe that's a disadvantage if you want to control edits).

At any rate, we do have tools (qRules and Doc Deployer) that can help to create this workaround. Free trials exist. qRules and Doc Deployer can be installed for free but the script to convert the files will likely take a couple hours of our time (one support incident).

That's the only option I can think of for now.