In the past,
- I would put the people list (Detail) in a different tab2. .
- On Tab Change I would save the Master Record and use its Reference for the Detail records
The problems are
- This is a web application, so the continuity is a bit more fragile
- If the booking was never completed,
- The Master Reference was lost.
- And people hated it.
- For a few countries, the tax department took that as a sign of fraud by the client. So I had to retrofit a background task to recreate cancelled records for missing References.
How are others handling it?
A thought that comes to mind (I am not enamoured by it, but I can make it work)
- Use a unique (negative) number for this session as a Master Reference for Detail records.
- If the booking is abandoned, I can just ignore / delete these.
- If it succeeds then I can have a process on the server that links them up and corrects the Reference.
P.S., that’s not my layout. That’s part of the spec sheet. I got the Client to draw all the forms up, so I could see what they were thinking.