rmicone
asked on
Split row data into separate files using Infopath 2010 rules or custom code
I've been evaluating InfoPath 2010 using sharepoint recently, and I want to see what the level effort would be to accomplish the following
1. Users would input field data in a repeating table
2. Click a button and have it take all records matching 'field1' and put that in a new infopath form file, then the values matching a different value in 'field1' and put that in a 2nd InfoPath form file
3. user could then submit each file individually
Is this difficult?
Can it be done using rules (doesn't look like it...) Is the custom code option too time consuming?
Can it be accomplished easily or should I focus on processing the file from the forms library once it's uploaded?
If anyone has done similar, or has some code examples, let me know, thanks!
1. Users would input field data in a repeating table
2. Click a button and have it take all records matching 'field1' and put that in a new infopath form file, then the values matching a different value in 'field1' and put that in a 2nd InfoPath form file
3. user could then submit each file individually
Is this difficult?
Can it be done using rules (doesn't look like it...) Is the custom code option too time consuming?
Can it be accomplished easily or should I focus on processing the file from the forms library once it's uploaded?
If anyone has done similar, or has some code examples, let me know, thanks!
ASKER
well let me give a little more data, basically it's a repeating table which represent line items, but my users want to be able to enter 50 lines, with different ship dates. So the field that will distinguish the grouping is the 'ship date' field.
So you are saying the submit rules can query by that field which in this case is date, and send those line items and corresponding field data in the line items to a separate form?
and is this available in ip2007 and ip2010?
So you are saying the submit rules can query by that field which in this case is date, and send those line items and corresponding field data in the line items to a separate form?
and is this available in ip2007 and ip2010?
Yah.
So as they enter a shipment. They submit after each one and is submits the data to SharePoint. Which can be conditional based on the date.
Why do they want the data seperated by date? You can have all of the data in one list and then allow them to use filtered views to see just one date at a time later.
Have you looked in 2010 of just making a list and customizing the entry form?
So as they enter a shipment. They submit after each one and is submits the data to SharePoint. Which can be conditional based on the date.
Why do they want the data seperated by date? You can have all of the data in one list and then allow them to use filtered views to see just one date at a time later.
Have you looked in 2010 of just making a list and customizing the entry form?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
scope
To sum up.
You want user to enter data for type field1 and for type field2 and you want a common starting place (form)
I would have one form.
The user selects the type (Field1 or Field2)
They enter one record and submit.
The submit rules look at the type and submit to a different form library based on the value of type.
They enter another records and submit, etc.
So the user enters the same amount of data they just file each record rather than at the end and you have to sort through the whole batch.
An analogy would be a paper form and filing each one as you filled them out rather than stacking them up and then having a seperate process to access the stack and file each one.
This solution would be real simple and straightforward out of the default features without any complex code or hocus pocus.