InfoPath Dev

Maybe this isn't possible and I am spinning my wheels...I don't know. So here it goes.

I am attempting to take one form that has 4 different views. 3 are different and one contains all items.

I want each of the specific views to be submitted to a different data source. I know it is possible to have multiple Submit Data Connections, but is it possible to Submit only certain data to certain connections?

What are you submitting to?

Give me more description of what you want to accomplish.

I one InfoPath form with 4 views.

All, Meeting Minutes, Project Outline Document, and Work Orders. I am attempting to have 3 different Submit options so that the POD view goes to one SharePoint library, the minutes to different SharePoint library , and the WOs to an e-mail.

 Is there a way to associate specific fields with a submit connection instead of all fields being connected to one submit connection?

Hope that clarifies it enough. Let me know if you have more questions! Thanks.

OK

The challenges with breaking up your form is that there is a consistency issue. I am guessing these are just read-only views but if yoiu seperated them then they could not really be updated unless you used a central data repository.  I would think seperatimg your data would not be good.  I would recommend one library.

You can switch to a view on open or create a menu view to select what they want to see. You could also base this on a user, their department or role or something what they would see.

You can also set a field in your form that controls the state.

Then you can check it on open and open the specific view based on its value.

So on submit set to all and submit to library1

then set it to pod and submit to library2

then set to minutes and submit to library3

finally set it to wo and email it.

Then the form would check the value on open and show the correct view.  I am not sure that is really best practice but would do what you would want. There would be all the data in each copy but the user would only see the subset you wanted.

Thanks for the insight.

I don't really care if the documents are linked after they are originally opened.

The concept behind all of this is that we have meetings all the time that require minutes to keep track of attendance, topics discussed, etc. It would be nice if all of these documents were at a user's finger tips to fill out when in a meeting instead of having to fill out minutes then a POD and then create WOs to the helpdesk after the fact.

Meetings often lead to PODs. And POD's always lead to WOs. So the connection of these 3 forms would be a one time deal and I don't care if they are not linked after the initial fill out.

With that said, any more thoughts?

Yes that makesa a lot of sense and I have worked with this type of form.

If I was going to design it. I would have one form. This is much simpler and all of the data is available in one form with out any more navigatio then a button click. Otherwise they have to navigate to various libraries to review.

You would detail the meeting possibly listing a department or project.

Create a list of attendees.

Have an agenda, which can be a rich text field for pasting or an attachment.

Then when action items are created you can assign them to attendees.

With an AD tool, you can even generate the email list for those with action items.

Notes can be entered etc.

Most of these items would be repeating items.

I have seen this all on one page but you could create a tabbed type view or seperate views for each section.

That way they load it once and with one click get to the data they need.

If you would like to see a demo of a meeting form then contact Qdabra for a demo.