As some of you have asked me, here is the "basic structure" of my multiple line items, I use in my business. It is particularly useful in the case of a customer order being splitted in more than one invoices.

Hope this is not too "messfull". Please tell.

I tried to make it the clearer I could.

This structure use a lot of lookup fields (indexable) and a set of multikey you can use for relationships.

Best regards to Steve BROWN on this forum for his help.

OK, as I said, I tried to make it the clearer I could...

As this is a single file, I couldn't re-create what can be performed using the 4 related files. It is just a simulation. So do remember that the Value list in this example is not conditional at all.

In the definitive file, you couldn't have listed all the operations, but only those related to the "operation" you are performing (the list of previous shipment would not appear when processing a customer order...).

Just follow the single example I gave to you to see how the keys and relationships evolves according to the operations processed.

Finally, there are 2 ID'S in the file :

- Universal ID is used to group all records with same Product_ID and Quote/Proposal N