So, you have:
- table of Invoices
- a table of tickets
When you enter a new Invoice it will have the supplier's ID. Rather than a pop-up you could have a portal on the screen that lists all the tickets (from the Tickets table), for that supplier, that are currently not allocated to an invoice.
The user could click on the portal row showing the ticket they want to assign to this invoice, and a simple Set Field step would allocate that invoice number to the ticket, and it would drop off the portal list (and appear on the portal list of this invoice's tickets that you would doubtless have on the screen also. One click on a line of its portal would unallocate a wrongly-allocated ticket.) Is that what you mean?
That would work as long as you could select multiple tickets for one invoice. Or would the set field step attach the invoice number to the ticket instead of the other way around so that there would only be one invoice number for each ticket, but the second portal would show a list of all tickets that had that invoice number?
Thanks for you help it has definately given me an appraoch to try!
Give the ticket record an invoice number. Then your tickets table becomes the typical line items table associated with the typical invoices table. A portal to them will list the ticket records and a list view layout based on tickets can include data from the related invoices--the most flexible way that you can print your invoice.
"Or would the set field step attach the invoice number to the ticket instead of the other way around so that there would only be one invoice number for each ticket, but the second portal would show a list of all tickets that had that invoice number?"