Turn off Quantity

[gjh42]

So each of the "small blue shirts" the client is buying goes to or relates to a different applicant?
If this is the case, it would seem reasonable to inject the applicant name or whatever identifier into the attribute structure. That would automatically make it work to display a product for each applicant.

I don't know how the client is supposed to indicate the applicant involved with each item... if they type in a name, that can be a standard text input attribute, which you can work on after processing to put the name in an "applicant" table in the db. (It will be in an "orders" table already.)
If they are supposed to select an applicant from an already populated db, there could be some sort of processing to put that into the option values and product attributes... can't say more on this as only you know how the base is set up.
What sort of scale is involved here? Dozens/hundreds/thousands of clients? Dozens/hundreds/thousands of applicants?

[conboy]

Glad the image helped.

Exactly, the applicant is what I want to be identified as being unique. As for you suggestion to associate it withe the existing attribute structure, I feel that is what Im doing already, but how does zc recognize that an attribute is unique. The code for this has eluded me.

The answer to your second question: the products will never exceed 260 but the number of applicants is potentially endless.

Thanks alot for the continued interest in my quest to reverse engineer this.

[gjh42]

The next relevant information will be whether the client can type the applicant's name into one or more (first & last name?) text input boxes, or if the applicants are already in the db and need to be selected.

The first method means that all you need to do is copy the text attribute info from the order to the "applicants" table in the db. The shopping cart, invoice, etc. will show the individual products with the associated applicant name.

The second method will require some more sophisticated coding.
If you were "associating it with the existing attribute structure", it should be treated as unique already. Exactly what sort of coding do you have to gather the applicant info?

[conboy]

The customer has to select the applicant from their account prior to selecting product/attribute. The applicants id is selected and stored just as other attributes in the database.

If I could populate a dropdown attribute select at the time of entering the product_info page, that could be on alternative, but I have not yet seen how to dynamically populate a dropdown in zc.

Well, I'm going to keep trying.

Thanks.