InfoPath Dev

Thanks Patrick, that's something that they don't tell you in the books. I'd already released a new schema with a required field on when you replied but I've now managed to get it all back up and running again. Because the relink documents function was broken for the new schema I had to programmatically move the forms to a new ...

Well I worked out how he did it. I'd still like to know how others do it. The developer before me created loads of additional fields called field1 field2 etc and used these to store any additional form variables that he needed to add so that the schema didn't alter. This doesn't make my life any easier but at least I know why ...

 The only thing I can think of incidentally is writing a custom upgrade script each time to handle stuff. But I can't see any evidence that he actually did this.

 I often have to make schema changes to existing forms. Every time I do this the view needs to be rebuilt even if the published form fields don't change. I keep getting told that the guy before me had a way of doing this without destroying and rebuilding the library views. I've had a good old search on this and I can't work out ...

Thanks, that's really useful

Thanks Qazi, Every InfoPath solution is a messy solution.

Hi again, I've been tasked with changing a datasource for a drop down list. Now, technically I know how to do this but wonder what effects this will have when viewing existing forms. There is a sharepoint list set up of clients and I intend to change this so that this list is pulled from a CRM system. The problem I have is that it is highly ...

In the end I built a workflow in sharepoint designer to move the forms and triggered it with the code below (A Console App)  using System; using System.Collections.Generic; using System.Linq; using Microsoft.SharePoint; using System.Text; using Microsoft.SharePoint.Workflow; using System.Web.Mail; namespace ...

There is an Excel service which is run from the sharepoint list and it has thousands of records in. It times out excel while retrieving the data and will shortly reach the maximum number of excel rows. The views aren't a problem. I could split the view into older and newer items but I don't think this is the correct solution as it is ...

 One of our InfoPath libraries has become so large that we need to move it's contents to another infopath library. Obviously moving this many files through windows explorer isn't an option. The "Open forms in windows explorer" just won't cut it for this many files and frankly it crashes far too often.  I suspect ...