Conversation
|
|
||
| **Copying rows** creates duplicate seat IDs as well as combination of zone, row number, and seat number. | ||
| Change the row number of the row you copied to an number that is not yet in use on the plan. | ||
| Then, activate the "Reversed" toggle and deactivate it again. |
There was a problem hiding this comment.
In my test, this step is not necessary if I already changed the row number.
There was a problem hiding this comment.
Changed the row number when?
Copying rows without this step results in failed validation for me every single time
There was a problem hiding this comment.
Not for me, if you want, we can do a quick screenshare session tomorrow
| 3. a custom string defined by you | ||
|
|
||
| The editor will assign seats the first option (UUID) during creation if you do not change any of the defaults (row or seat number). | ||
| If you change seat or row number, or if you use the "Reversed" toggle, the editor will assign the second option (zone, row number, and seat number, joined with dashes) as the seat ID. |
There was a problem hiding this comment.
Still not happy with the Reversed toggle as the trick here, without explaining that the Reversed toggle is actually for. But that might be a software UX issue, not a docs issue ;
There was a problem hiding this comment.
Is there a more straightforward way to do this?
There was a problem hiding this comment.
No, that's what I mean: I don't like it, but it's a problem of the software, not of your docs.
3 participants
Explain how to set up seating plans and layouts, and how to sell tickets that way