dont know if this is a real issue but i used to load an entity screen where my clients had there returned bottles(basicly a modified customers entity screen) from out my ticket but now since i updated to .62 this doesnt work anymore. i allready found out that the issue only occurs when im in a ticket if i set the automation command in navigation display it goes to the entity screen.
normally i tap the retour bouteille button like shown bellow and then it should load the screen shown in pic 2
just checked it all and they all are correctly written, i also added “retour cash” to entity type but also that didnt help for now i will downgrade back to .60 as i stated that its very important part for my restaurant but will post the full setup i used so it can be recreated and maybe that way the solution can be found
sorry my bad forgot to put setting back to how it used to be there as i tried to get the regular customer screen and see if that worked(which also didn’t work) will put right ss up right away
dont really understand, the ticket is still unpaid when we use the retour bouteille button cause for when it does happen that the ticket is paid before entering the retour bouteille entity i have setup the reopen ticket button/rule (Re-open Settled Ticket & Cancel Payments)
tried it but that doesnt work, it just keep on ticket screen. tobe sure if it worked i tried it from navigation screen and then it just opens a ticket but it doesnt give me the requested entity screen
no i checked all that(it used to work even with locked tables in previuos version)so far what i figured out it only wont open entity screen when im in a ticket
will check rule again can be i still have update state in there
Navigate module action will not create a ticket so did you try that action like I said? It works fine in 5.1.62 when I use it. So something is wrong on your setup.
If ticket is locked it won’t let you change entity.
So you have some kind of automation going on and it’s conflicting. I see your assigning a user as ticket tag. What automation are you using to do that?
Check for any execute automation command rules that have no custom constraints.