part definition?

[snuggster.com]

i have a tricky question (at least in my mind)

i have the following files:

invoice, line items, line item options

they relate as follows:

line item options -> line items, line items -> invoice

------

now for the question?:?

im trying to get a report or layout (on the invoice file) that will print as the following:

--------------------------------------------------------------------------

someone.com (lineitem)

----design (lineitemoption)

----web space (lineitemoption)

example.com (lineitem)

----monthly maintainance (lineitemoption)

-------------------------------------------------------------------------------

this way those options if you will, create the line items as a package, so that the lineitemsoptions are options of the line item. i can figure out the calc to do that but the question is how do i make the line item options show up in possibly a part defination or etc. because i dont want to do this in a portal because it wont print correctly, there are no set number of options.

someone please help!!, i will give more details as needed!!!!

[Ugo DI LUCA]

Hum.

You have Line Items, Line Items Options and Invoices.

Where are the Items themselves ? Or are these Items options ?

If my assumptions are right, you can do such a report in the Line Items. Why would you like it in the Invoice file ?

If instead someone.com is an Item and under it goes the Options, then you'd need to script it or rethink the way the Line Items is structured, so that it shows the Children (Items) and Grand Children (Options).

In this case though, I'd think you need another join file from Items to Options.

HTH

[snuggster.com]

im lost on what you mean, maybe this will clearify what i was saying too.

the line items are in a relationship with the inovice.

the options are related to the line items

so those line items or options can import a product from a product db. my thinking was so that i could have the line item as a package price, with sub items / options. help me!!!

[Ugo DI LUCA]

Hi again,

From what I understood, if you choose Option#451, you'd got say Product#2, Product#7 and 9 entered in the line items.

I'd guess that there is a many to many relationship from Options to Products.

Are you invoicing Options only, or do you invoice Products alone as well ?

This would be important to decide which method you'd finally rely upon.

It's just a matter of how you'd structure the line items.

However, this would necessarily be scripted.

[Ugo DI LUCA]

Hi,

Check this thread as it deals with components and products, which is quite similar, and has a test file (v5) with what you're looking for (I think).

ManyToManyPortals

[snuggster.com]

maybe this will help me to explain better. im not good at explaining myself, i appologize.

the bolder items in the 2nd image are the line items, those under are the lineitemoptions, they act as options of the line item. so that the line item is a "package price" if you will. so the line items and options get data from the same product database. my idea behind this was to have a packaged price, or options to add on to an item.

ex: instance if i sell a website, a filemaker solution, and print work. those would be line items. the options of those line items (lineitemoptions.fp_) would be:

website

----design and setup

----webspace

----dot com

my question is though, is this necessary to do what i want to do

which is make the lineitems as a package price which adds up the price of the options to that line item, but my real problem is how to i get it to print, i can do this with the relationship i have right now in a portal. it wont print correctly that way because i could have several amounts of options to a line item.

any help is greatly appreciated. thank you much.