Terminal Print Job Mappings

[Posflow]

Problems seems to be that SambaPOS does not evaluate other print job mappings in case:

• Terminal column mapping is set and others are * —> It will result in * terminal mappings being skipped.

In the photo below. If order submitted from Restaurant terminal, only the Beer category will be printed. Other will not.

mp4 in zip file
Print Job Mappings Issue.zip (3.4 MB)

[markjw]

This is a long standing bug, I reported it back in April 2019 on v5.2.22…

Problem with terminal mapping on print jobs

I have noticed in v5.2.23 beta, and also in v5.2.22 that the Terminal in Print Job mappings appear to be ignored. I have tested like this: [image] 2 terminals each are sending to a different network printer to open the cash drawer. When I test this scenario, no matter what terminal the print job is executed from, POS1 cash drawer is opening. If I delete the POS1 mapping and only leave POS2 mapping, then as expected POS2 cash drawer will open. So it would seem Terminal is being ignored / n…

The only way to get around it is to create separate Print Jobs for each terminal then trigger then separately in rules. You can simplify the amount of actions you need to create by just passing the terminal name as a parameter, but this is still the only way I could get it to work per terminal in a reliable way.

[Poscu]

Or adding lines for each terminal in the same print task.

[markjw]

@Poscu

adding lines for each terminal in the same print task.

Assuming you mean print job and not print task? However this doesn’t work, it is the issue which has been reported here.

[Poscu]

I think we couldn’t agree because of the different expressions of Samabpos in Turkish and English. In the Turkish version it is “Print Task”, in the English version it is “Print Job”. If I select a terminal in a line in a “Print Job” and select the terminal field * in the other lines, the print task does not work correctly. I mentioned this. But if I adjust my lines by selecting the other terminals, the problem is solved. Of course, you know better… I am a novice, maybe I answered without taking the liberty.

[markjw]

@Poscu

But if I adjust my lines by selecting the other terminals, the problem is solved

That’s interesting, its definitely not something I have tried. However the problem still exists as this is still just a workaround, * should work for terminals the same way it does for anything else but doesn’t.