I use it to track how many minutes ago the order entered and who entered it. how can it be more practical???
Get a faster computer.
@omerfarukulusal the sample you posted is a report template. I don’t think this is what you’re using. Can you post your full state format here?
The time shouldn’t be an issue as it’s directly linkable to the entity but for ticket user with that report expression it is going to require much more processing as it’s not looking at the entity it’s looks at all your tickets to find the users for tickets with remaining balance and it has to check through all tickets for each entity on your screen.
If your computer cannot process this at the speed you expect you might have to think about alternate method - perhaps new custom entity state for field which gets updated in a ticket entity changed rule so you specify the current user on the entity itself.
Thank you. İ understand. But i cant find a solve.
I suggested an alternate method.
You don’t detail your use so hard to say best but if you have waiter assigned to tables you could do many ways including user specific entity screens and others.
try changing
... and T.RemaningAmount > 0
part to
... and 'RemainingAmount > 0'
Please let me know if it makes a difference or not.
1 Like
What is your SambaPOS version?
My versiyon is 5.60.
This feature released with 5.1.62 version.
If you attempt to upgrade please create a backup to ensure you’ll be able to roll back to 5.1.60 if you need to.
5.1.60 released more than 2.5 years before. It will be a good idea to test your backup with latest version on a separate computer before upgrading production system.
How do I show the {ENTITY STATE MINUTES:Status} only when a value exists, e.g. when a ticket is less than 1 minute old, {ENTITY STATE MINUTES:Status} contains no value and so it shows on entity screen like this:
I have tried
[='{ENTITY STATE MINUTES:Status}' == '' ? '' : '<br/><color Red>{ENTITY STATE MINUTES:Status} min</color>']
and
[<br/><color Red>[{ENTITY STATE MINUTES:Status}] min</color>]
but neither are parsed when the expression or conditional operators are applied.
I notice others seem to have the same issue above in the screenshots but it doesn’t seem to have been addressed.
Use greater than or less than instead of == see if that works.
No, the problem is it does not parse the expression at all. I think expressions are not available for entity display format. So wonder if there is another way?
Would you not want to use TN() if using greater/smaller?
1 Like
True, my mistake… but again regardless, it doesn’t get parsed. So using an expression is not the way…
[=TN('{ENTITY STATE MINUTES:Status}') > 0 ? '' : '<br/><color Red>{ENTITY STATE MINUTES:Status} min</color>']
I have overcame this in the past let me look and see what I did. Off top of my head i swear I used a script.
Now you mention it, yeah I think I may have done something the same myself