Sending more values from one dropdown to another

[Joy68]

Hi,

I need to pass multiple values from a dropdown list (text, 20 repetitions) on ESTIMATE layout to another dropdown list (text, 20 repetitions) on BOOKING layout.

On ESTIMATE layout I compile list of equipements (with relative prices) a customer requested then create PDF file from it and send it to the customer via email.

Once the estimate was accepted by him/her I reopen the ESTIMATE layout, click on button created by me which opens BOOKING layout, creates a new record and pastes values from REQUESTED EQUIPEMENTS dropdown list to an editbox field.

This works well but...

What I really want/need is the values to be pasted into a dropdown list (text, 20 repetitions).

No matter how hard I try it always pastes only the very last item from the list of equipements compiled on ESTIMATE layout.

The reason I'm not happy with editbox solution is because If I want to create manually a new record on BOOKING layout I must compile booked equipements choosing from the same dropdown list exactly the same way I do on ESTIMATE layout.

What my "Create Booking List" button does is:

- Set variable $Items, Value: List ESTIMATE::Items

- Goto layout BOOKING

- New Record/Request

- Set Field BOOKING::Items;$Items

In few words I must be able to create Booking record either by clicking on my own button or by clicking on Create New Record in RECORDS menu and stil being able to choose items from dropdown list.

So, how do we send, say, 9 values from one DDL to another one?

Hopefully someone here already managed to accomplish such task!

Thanks in advance, Joy.

[bcooney]

Welcome to the Forum!

This question comes up very often, converting a Quote to an Invoice, Estimate to a Booking. Whatever; different terms for the same thing. The common element is that you wish to share line items (maybe all, maybe select some) between two parent entities. That is, take some of the Quote line items and add them to an Invoice. Perhaps, add items that weren't quoted. Meanwhile, keep track of what's not invoiced....

Your structure however apparently uses repeating fields. I think that is what you're describing when you say "drop down list with 20 repetitions." This is not the correct way to structure the data.

Please see the enclosed demo, which illustrates the proper data model for sharing a line items table between two parents. I know this is a huge change for you, but it is the correct way to do it.

QuoteInvoice.fp7.zip

[Zcast]

Yep....Barb is absolutely correct. Here is my attempt....I created the Estimate ID and Invoice ID to be the same, so there is no confusion between the two in general use.

Estimate.zip

[Joy68]

Hi,

I'm afraid to be still far from understanding relationships and portals

I have those two layouts: ESTIMATE and BOOKING.

I click on my customized button within ESTIMATE layout to create a new record in BOOKING layout with exactly the same items chosen in ESTIMATE portal. But...

if I add an extra item on BOOKING layout and then go back to ESTIMATE layout I find this extra item automatically added to estimate items list too, which is something I absolutely don't want to happen.

Once the estimate has been compiled it MUST remain as is, even if I modify later the booking record after it was created from it's "estimate mum".

How can I prevent this undesired BACKWARDS ITEM LIST UPDATING thing?

Both ESTIMATE and BOOKING portals show "Show related records from: ESTIMATED ITEMS" in Portal Setup popup. Could it be the cause?

I must admit I used Zcast's example file to reproduce the structure the way I needed it to be. Haven't changed the relations between tables though.