Hi there @Greg_Noonan!

I think you’re probably missing a junction table in your base structure. Take a look at my example base for invoices and line items:

The base is structured to allow for multiple quantities of multiple items on an invoice (or in your case, an estimate).

I hope this helps to point you in the right direction! Happy to answer any questions you might have.

This makes sense!

Just to make sure I follow:

“Items” is your product catalog, and sets the pricing.

“Line Items” is where you’re constructing the actual invoice

“Invoice” is basically just used to summarize the “Line Items” info into a customer facing document and to facilitate the final business math?

Can you summarize your workflow with these 3 sheets if you don’t mind - I think I’ve got it, or at least can make it work, but I want to double check.

Thanks either way!

Hi Greg!

Yes, looks like you’ve got it down!

oItems] could be considered a product catalogue - each item is unique and has an associated price

rLine items] is where the invoice is constructed; where each record pertains to one {Item} and one {Invoice}. This is where varying quantities of varying items can be recorded.

dInvoice] is where you can sum up the total and assign the document to a customer. It’s also where the Page Designer block should be pointed if you want to use it to create an invoice or estimate.

When I’m constructing an invoice, I generally do everything from the aLine Items] table.

Hope this is helpful!