InfoPath Dev

Hi Everyone,

I was wondering if it is possible to have two seperate repeating tables copy information into another repeating table.  For example, let's say that I have repeating table customerA and repeating table customerB and finally I want to write the information from both of these repeating tables to repeating table CustomerInformationAB.

> Customer
   > Customer A (repeating table)
         > CustomerAccNumA
         > CustomerNameA
         > CustomerPhoneA
   > Customer B (repeating table)
         > CustomerAccNumB
         > CustomerNameB
         > CustomerPhoneB
   > CustomerInformationAB (repeating table)
         > CustomerAccNumAB
         > CustomerNameAB
         > CustomerPhoneAB

customerA Repeating Table
Customer Account Number              Customer Name                Customer Phone Number

123456                                           Joe Smith                         555-555-5555
123458                                           Jimmy Smith                     777-777-7777


customerB Repeating Table
Customer Account Number              Customer Name                Customer Phone Number

123457                                           Jane Smith                        666-666-6666

customerInformationAB Repeating Table
Customer Account Number              Customer Name                Customer Phone Number

123456                                           Joe Smith                         555-555-5555
123457                                           Jane Smith                       666-666-6666
123458                                           Jimmy Smith                    777-777-7777

 I hope this makes sense.  Thanks again.

 Bryan

Hi -- you can't add rows to a new table without code (or qRules, currently free and available here). But I'm curious -- why the two repeating groups in your data structure if they both collect the same information?

Hi Hillary,

It is actually different information.  What I am doing is taking orthodontic (braces and stuff) general information (part number, category, etc.) in one of the tables and then in the other table it contains preweld perscription information that is unique per customer.  In essenence some of the data is the same, but I have to have it where it looks at Account number only if there is a Preweld Prescription card.  So I created two SharePoint lists one that contains all part numbers with no perscriptions and the other contains part numbers with perscriptions and account numbers.  Hopefully this doesn't sound too crazy.  Ultimately what I need it to do is export to excel only quanity and part number, so we can upload it to our database.  I have seen you mention that qRules, quite a few times so I will download it for sure. 

 Thanks for the response.  You are awesome!

Bryan

It has a copy table function that I wish I'd had when I was first working with InfoPath and didn't write code, that's for sure. And no, what you are doing doesn't sound crazy -- but when I looked at your sample I thought "huh", since your sample showed all the same fields. Made me curious.

The problem you may have with Copy Table for this would be if you have tables with different numbers of fields, and it sounds like you do. So, I wonder -- do these items need to be in separate lists in SharePoint? Or can the be in one, where some of them have a prescription and account number and some don't?

Hi Hilary, 

Thanks for the quick reply!  The value for Part Numbers would be different as we have 10,000 some odd parts and of course quantity would very.   However, there won't be a situation where on one row we need to have account number, but not on the next row.  As far as merging the data into one sheet I tried that, but I couldn't come up with a creative way to limit account number to perscription.  For example:

Let's say I have handful of parts:

Account Number         Category               PartType      PartNumber      Quantity      Angle      Sample
123456                  Maxillary 1st Molar      Lingual          0A01234             10           -1        99-99-1459   >>>> This would be considered a perscription
                             Maxillary Right                 3             0A01256              3                                          >>>> This would be considered a regular part       
                             Maxillary Right                 7             0A01689              7                                          >>>> This would be considered a regular part 
                             Maxillary Left                   G+           0A01785             10                                         >>>> This would be considered a regular part      
125678                  Maxillary 2nd Molar      Buccal          0A06845             10           -1        99-99-1459   >>>> This would be considered a perscription 

Ultimately what would happen is the part numbers that were selected would flow into an easy to export list just below:

PartNumber      Quantity     
0A01234             10   
0A01256              3    
0A01689              7       
0A01785             10        
0A06845             10    

 Then what I would like to do is have it basically hide the row if Account Number is present unless AccountNumber (SharePoint List) = AccountNum (InfoPath).  I haven't come up with a good way to do that.  Anyway, I real appreciate you and your talent.

 Have a great day,

Bryan

I'm having a hard time understanding, I'm afraid. Could we maybe move the conversation a level higher and talk about the business logic? That is -- you currently have data in SharePoint. You are using InfoPath to.... what? As an order form of some kind? And then the user exports each filled out form to Excel....to load into another database? I might be able to help a bit better if I knew a bit more about what you are doing....