Hello everyone,

i have attached the file for anyone who may be able to help. questions are in file.

What the issue(s) are is.

1. when the user chooses an ITEM - they have to then choose which type it is & based on that, a global relationship is established using a script and another LineItems TO which has specific details to choose from.

2. IN those options i would like to have user choose [qty -- flavor] ( dont know how to do that within portal )

3. Then if i would like to print the final invoice, what i would need to do in order to eliminate any issues.

thanks,

i

pos Copy.zip

got another issue. that perhaps i can have just a portal with a drop down list that can tell when user has

selected lets say ('suite') using patterncount(), then based on that selection is shown options such as

please choose stand color

cake flavor

cake filling

cupcake qty(s) & flavor

due date

Message

Style #

etc

etc

-thanks

I think I have seen this question several times already, and I didn't understand it. I do not understand it now.

In general, the method for dealing with options for invoiced products depends on how uniform the choices are. In the easiest scenario, all products have a color (one of five colors) and a size (one of S/M/X/L/XL). In a more complex case, each product can have its own set of colors and/or sizes. It gets really complicated when each product can have its own optional attributes, e.g. Product A comes in 5 colors, Product B comes in 4 sizes, Product C has a standard/luxury finish and Product D has all of those.

I haven't been able to determine which category your issue falls into. In you example, ALL line items have the same attributes:

• stand color
  
• cake flavor
  
• cake filling
  
• cupcake flavor
  
• cupcake topping
  
• message
  

Ok. Let me Clarify;

cakes have these

• size ( eg , cf-8, cf-9, cf10,cf12
  
• type ( buttercream, fondant, creamy fab)
  
• filling
  
• flavor
  
• notes
  
• style #
  

Pull aparts

• cupcake flavor(s) ( requires multiple cupcake flavors & qty's)
  
• style # ( same as above)
  
• amount ( ,eg. pa-12, pa-24,pa-36)
  
• notes
  
• size cupcakes ( eg, teeny, shots, med, large)
  

Suites -

• (has 1 cake & 24 cupcakes)
  
• or 1 cake ( 48 teenies)
  
• or 1 cake ( 36 shots)
  
• cake flavor
  
• cake filling
  
• cupcake flavor(s)
  
• cupcake size
  
• message
  
• style #
  

Common information for any of thes orders will ALL HAVe

• due date
  
• due time
  
• Message
  
• style #
  
• delivery ( yes | no )
  

i hope that clears up some.

-i

i hope that clears up some.

To some extent it does. Unfortunately, it's even more complicated than I suspected, since some of your products are "kits" made out of other products. So basically you have three issues here:

1. How to break a "kit" into multiple line items of the component products;

2. How to record the different options of different products;

3. How to build the user interface to handle this complexity.

I don't think all of this can be solved within the confines of a forum thread. On the bright side, if this is a POS solution, you can take advantage of scripting to walk the user through the necessary choices and hide the underlying complexity.

I would agree with you. I thought it was complex as we offer so much customization, hence the custom POS solution as there are none out on the market currently.

Should i just script with prompts to ask questions and add to OrDER# or multi-related portals> Really would appreciate direction on making it a bit less complex for my users.

thanks

-i

IMHO, you need two "line-item" tables - one to record the products "as ordered", and another to break these into their individual components.

If, for example, an order is for for 2 cakes and 1 suite (1 cake + 24 cupcakes), the first table will have 2 records ( Cake x 2, Suite x 1) and the second table will have a separate record for each cake (3 in total) and for each group of cupcakes (assuming one can split them into different flavors) - so that's up to 27 records.

Which is what i am doing now thanks to JBante. it is just trying to tweak the interface and make it super easy for my users to actually

enter in good data except garbage. Such a hard task!!! SHEESH>>>

when i have done more, will upload for others to give input.

sd2.fp7.zip

OK, i have something i think will work thanks to Comment.

What i am doing is creating a relationship with

 suite»Items table 

so on a "dashboard layout" , customer will choose to create a "Suite kit" or "Cake kit", this will take them to another layout creating the

necessary relationship, but now i want to bring them HOME to show

ALL the data on 1 layout but i dont know how to do that.

For example;

for 1 kit , the ordered 2 suites

1 cake kit

4 pull apart sales

regular sale or 7 cupcakes, 10 cookies,etc

HOw can i accomplish that or i cant?

thanks,

-i