You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we can print a receipt without specifying uniqueSaleNumber. In this case the printer will automatically generate and add it to the receipt (at least with Datecs devices). However this auto-generated uniqueSaleNumber is not returned back which make it impossible to print a reversal receipt afterwards.
Is it possible to get the uniqueSaleNumber back with the response, no matter if it is already specified by the incoming POST request?
Thanks,
Dimitar
The text was updated successfully, but these errors were encountered:
This could be made and would be a nice addition to the protocol.
However, as this is unsupported open-source effort, it is up to you to implement it. If you implement it with a quality code, please give us a pull request, so that we can share it to benefit everybody.
If you decide to implement it:
Implement it for DATECS printers
Consider the non-DATECS printers - do they support this?
Include the change in the protocol help (this should be only 1 line description and 1 line in any of the example responses)
Anything else, which you might consider good for the quality of the pull request.
Hello,
Currently we can print a receipt without specifying
uniqueSaleNumber
. In this case the printer will automatically generate and add it to the receipt (at least with Datecs devices). However this auto-generateduniqueSaleNumber
is not returned back which make it impossible to print a reversal receipt afterwards.Is it possible to get the
uniqueSaleNumber
back with the response, no matter if it is already specified by the incoming POST request?Thanks,
Dimitar
The text was updated successfully, but these errors were encountered: