multiple line item options how to

[imoree]

hello everyone;

my first thing is i have a simple invoice system that looks basic like this

customers -:Orders=: LineItems=: Products

my issue is i add complexity as i have a few individual lineitems Products which have additional options. So i have to add another join table; LineItemOptions which connect line items to a product options table( another TO of Products)

My thing is how do i make this more elegant or am i just being silly?

Eg.

User adds CustoM BAG ( product id, product TABLE)

then they want to add another option(3)

option1; leather strap with zebra print

option2; color black with pink inlay

option3; interior skin ( shark skin)

After these options are entered , it connects to the lineitems table via lineitemoptions , but how to make this look more elegantly rather than 2 portals?

Any ideas?

TIA;

-ian

[Ocean West]

are the options separate items stocked or do the election of options affect the price?

[imoree]

are the options separate items stocked or do the election of options affect the price?

THe election of options affect the price.

eg. If option 1 chose, $price increases basePrice by $15.99

etc.etc

then the options are Added to the line items and price of option if calculated

below to show final price with all options.

Also, the ability to print / report will be ok once options are included in relations correctly

thanks Stephen...

[Ocean West]

each option is a unique product with the price. as it may also take-up physical space on a shelf and have quality in stock. (unless it's manufactured on request)

or

in the product table build it so it is a hierarchy type structure so that it can be sorted all options would be level 2 under the main product.

[imoree]

unless it's manufactured on request)

It is manufactured upon request

product table build it so it is a hierarchy type structure so that it can be sorted all options would be level 2 under the main product.

This adds a substantial level of complexity that i can't find easy examples of doing. Any that you may know of that are less extraneous or is that

hierarchical structure. What about Entity attribute values-> i know these are hard /tricky to report on.

EG> Entity : Handbag

Attribute: Leather Strap

Value: $15.99

thanks,

-i

[Ocean West]

as far as the "interface" is concerned building something like this as a "picker" to add items to the invoice line item is relatively achievable.

http://www.excelisys.com/demos-free-filemaker-pro-downloads.php

There is a Hierarchal Portal Example there.

--

I have seen the entity attribute model as well but it can get very tricky fast in FMP especially for searches and reporting.

--

Product options can grow exponentially if you consider sizes and colors and other attributes.

[imoree]

I like the idea of a picker per say, anyone else have other ideas?

thanks Stephen , i am trying to learn what they did in that file http://www.excelisys...o-downloads.php. It definitely needs "studying" to make

sure the implementation and desired affect is achieved> something that can definitely be ported as well.

-i