InfoPath Dev

I need a little help from someone as to if this is possible, and how to do it.

I am creating an order form for users to place an order for software/toner/computers etc. Since i need to adapt this to work around our past paper form, this has made things difficult for me.

The current workflow requires that we fill out a unique IS Request form each vendor and then our purchasing group prints and faxes that to the vendors. So if we order a computer from dell and software from somewhere else, we need to fill out 2 forms.

I am attempting to allow users to place thier own orders by selecting the items that they wish to order (items come from sharepoint list) and submit that. I need all the items that are from vendor A to get dropped into the view with the req form for that vendor, and items for vendor B get dropped into another form for that vendor.

For Example:
user goes to form and wants to order a toner (from CDW), software (from CDW), and also a computer(from Dell). They select the approriate items from a drop down list. In another View, there is an IS Requistion Form (converted paper form) that is populated with all the CDW items on one form, and another instance of the IS Requisition form for the Computer. This can then be printed by purchasing so that they can fax each order to the correct vendor.

I have 3 Sharepoint lists created that we use to maintain the vendor list, the item list, and one for the user that has looked over and verified the order.

If i could get some pointers to help set this up so it is possible, i would be greatful! I had created a form that we use currently within our group that we currently use. Managers liked that, and wanted to create one that was dummy proof for the rest of our users, where they could place their own..

Thanks!

Hello,

If your item list contains info on which vendor an item belongs to this will not be too hard. I'm making some guesses with what I say below as I don't know the structure of your form's data source.

The trick is that once the user has made the selections they need to be sorted by supplier so that the IS Req form view can easily break out the items by supplier onto separate pages.

You will likely need to write code to resort the XML by the supplier node.

Then in the IS Req form view, you will create a repeating section bound to the repeating items. The trick here is that within that you put a section for your page header the fields for your items, and then a section for your page break. Then what you do is conditionally show/hide the header and page break based on if the supplier of the "previous sibling" is the same as the supplier of the current sibling.

On the screen it will look wierd since there will be multiple headers showing all in one big scrolling screen. But when you print it each supplier and its items will print on a separate page.

Let me know if you have further questions.