Looks like it doesnt work on v5.1.60, sure its something that would be sorted maybe.
Currently it voids the whole order format and shows blank.
Order grouping would be the other option obviously if you wernt using for combos.
Purhaps you could make something using entity screen as a display position format? Bit more involved but can imagine some options.
Yeah I am trying to setup positions in every way I can possible imagine and coming to limits every time.
One of my approaches was:
enter order for first position and click add ticket for next position but that doesn’t work because it submits the current position ticket when you click “Add Ticket” for the new position. Obviously we need all the orders to come out in one ticket at the kitchen.
To be honest im not familiar with what your referring to.
Dont worry, probably would take allot of work to get anything close to what you want but was thinking like a form of kitchen display but for positioned tables.
The printing only goes like that on default config, you can soon adjust the printing flow.
What might be better would be to do that and run multiple tickets and hold the orders in a ‘to be printed state’ then submit all at once.
Thing youll need to sort though is a way to print contents of multiple tickets as one print. The state flow is easily adjusted its just the actually printing as a single ticket thats the challange.
Not sure if you can offer print ticket action multiple ticket ids…
Hey how did you do this. Can I display my state like you did the word Gift and Hold?
Thats what I was thinking HOWEVER those are all fixed text/stings, you cant use dynamic {TAGS} in state formatting…
Thats what I tested a minute ago when I said it voids the state formatting for the order line.
I tried putting {0}{ORDER STATE:Status} and it showed nothing (in dark theme 
)
I tried to get rid of the dot on portion like i did on prints but doing {NAME} {PORTION} rather than the default which gives Product.Portion but doesnt work.
Haha yeah that sucks ;/
Hopefully emre comes up with something for us. Iv been thinking and im okay with the waitress having to manually click every order and move it herself each time. I dont think thats a big deal I just need them to be able to easily see the positions.
Could you not simplify that? If not wanting to automatically split ticket into ticket per position just have a select position orders with a ?Prompt or command value selector - they enter sat 1 and then the automation command rule uses a select orders action with state position =P[:CommandValue]?
So it automatically selects all orders for a position?
Then either move button or automatically move?
Could use that same flow to print the orders for a specific position on request also 
Tried that already. Unfortunately select orders action does everything in the backround so nothing is visual. Which can lead to confusion since waitresses dont see what they selected. I thought about this all long and hard and determined with current status of samba its best to just have them manually select everything and move it. Ill just need to implement button Q did in a tutorial to print all tickets for table at once which is one the main requests I got. Also If I can get a way to see positions easier that will be sufficient enough…
They are selecting them all to do what? move? so make a move position button and select/move in same automation…?
Yeah thats an option that im keeping in mind. i just discovered a way to tell waitress which positions are in each split ticket by using one of your report tags. Only issue is im getting a report with each value in a new line. Is there any way I can retrieve it with every value on same line?
Hmmmm, whats the code for that?
Might need to parse it through some jscript to remove the linebreaks…
Are positions always sequential? Could you not just count the number of positions and way there are x positions on this table?
{REPORT ORDER DETAILS:OS.SeatPosition.asc:T.Id={TICKET ID} :{0},}
Id like it to all be in the same line with 3 spaces in between
Preferable to always be in ascending order as well.
Probably easier if you dripped the P and just used numbers… THen can sort assending in report expression straight off.
Only reason i put the P was so that waitress knew that 4 actually means Position 4. I guess i can remove it.
Or put the number into state value on its own and leave the Pn in the state name?
Yeah thats fine, does state name show up in order line description tho?
its shows as StateName:StateValue if I remember corectly