Quantcast
Channel: SharePoint 2010 - Development and Programming forum
Viewing all articles
Browse latest Browse all 11508

Help needed architecting a SharePoint application

$
0
0

Hi, I am in the early stages of working on a new sharepoint app for a customer. They want an InfoPath form created that will capture a number of fields and submit them to some storage location within SharePoint. Once submitted, the relevant users will go to the new item and at certain intervals will have to add new data to this. 

I'm really unsure how to architect this. If capturing a form in InfoPath I'd expect to submit this to an xml file in some forms library. The problem is how can I cater for the additional set of fields that users will eventually add?

Should I stay away from submitting as xml and just have a list-linked InfoPath form, then use some workflow to copy the required fields to a secondary list which already contains all the required fields that may subsequently be filled in my the receiving team?

I think the critical point is how I can make the data captured via InfoPath accessible/editable and also merge it additional data. I would tend to think of it as a case management system whereby my IP form is the data capture system, but then this is also merged with a bigger data set. 

Any help around architecting this would be much appreciated.


Viewing all articles
Browse latest Browse all 11508

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>