QMX for SambaPOS ::: Cross-Platform Mobile Client


#25

It seems to be stuck in a loop trying to get the Departments.

Show a list of your Departments, Terminals, and Users.

In Chrome, try Ctrl-F5 to clear browser cache and reload.


The following is what a “normal” APP USER Authentication (Username/Password) and REGULAR USER PIN Login looks like, with a landing on Main Menu …

2017-11-04 11:23:37.640 [GETDATA] [MessageServerConfig] parms[] ...
2017-11-04 11:23:48.976 [GETDATA] [Users] parms[] ...
2017-11-04 11:23:48.976 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:23:48.998 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:23:49.008 [SQL] Fetched [Users] records[11].
2017-11-04 11:23:51.820 [GETDATA] [Departments] parms[] ...
2017-11-04 11:23:51.821 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:23:51.840 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:23:51.851 [SQL] Fetched [Departments] records[2].
2017-11-04 11:23:52.050 [GETDATA] [Terminals] parms[] ...
2017-11-04 11:23:52.050 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:23:52.070 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:23:52.082 [SQL] Fetched [Terminals] records[3].
2017-11-04 11:23:52.393 [GETDATA] [Workperiod Status] parms[] ...
2017-11-04 11:23:52.393 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:23:52.415 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:23:52.419 [SQL] Fetched [Workperiod Status] records[1].

And here when accessing POS1 (POSA) …

2017-11-04 11:35:22.237 [GETDATA] [MessageServerConfig] parms[] ...
2017-11-04 11:35:33.064 [GETDATA] [Users] parms[] ...
2017-11-04 11:35:33.064 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:33.084 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:33.096 [SQL] Fetched [Users] records[11].
2017-11-04 11:35:37.465 [GETDATA] [Departments] parms[] ...
2017-11-04 11:35:37.465 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:37.489 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:37.502 [SQL] Fetched [Departments] records[2].
2017-11-04 11:35:37.714 [GETDATA] [Terminals] parms[] ...
2017-11-04 11:35:37.715 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:37.735 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:37.753 [SQL] Fetched [Terminals] records[3].
2017-11-04 11:35:38.109 [GETDATA] [Workperiod Status] parms[] ...
2017-11-04 11:35:38.110 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:38.129 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:38.135 [SQL] Fetched [Workperiod Status] records[1].
2017-11-04 11:35:38.357 [GETDATA] [Order Tag Groups] parms[] ...
2017-11-04 11:35:38.357 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:38.380 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:38.406 [SQL] Fetched [Order Tag Groups] records[22].
2017-11-04 11:35:38.619 [GETDATA] [Ticket Tags] parms[] ...
2017-11-04 11:35:38.619 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:38.640 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:38.652 [SQL] Fetched [Ticket Tags] records[9].
2017-11-04 11:35:38.894 [GETDATA] [States] parms[] ...
2017-11-04 11:35:38.895 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:38.915 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:38.930 [SQL] Fetched [States] records[19].
2017-11-04 11:35:39.139 [GETDATA] [States] parms[] ...
2017-11-04 11:35:39.140 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:39.162 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:39.170 [SQL] Fetched [States] records[19].
2017-11-04 11:35:39.400 [GETDATA] [Entity Types] parms[{"name":"1","value":"'Tables','Customers'"}] ...
2017-11-04 11:35:39.400 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:39.425 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:39.431 [SQL] Fetched [Entity Types] records[2].
2017-11-04 11:35:39.664 [GETDATA] [Entity Screens] parms[{"name":"1","value":"Customers"},{"name":"2","value":"QMXterminal"}] ...
2017-11-04 11:35:39.664 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:39.687 [GETDATA] [Entity Screens] parms[{"name":"1","value":"Tables"},{"name":"2","value":"QMXterminal"}] ...
2017-11-04 11:35:39.687 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:39.691 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:39.713 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:39.735 [SQL] Fetched [Entity Screens] records[3].
2017-11-04 11:35:39.753 [SQL] Fetched [Entity Screens] records[4].
2017-11-04 11:35:40.175 [GETDATA] [Entity Screen Entities] parms[{"name":"1","value":"Tables"}] ...
2017-11-04 11:35:40.175 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:40.200 [GETDATA] [Entity Screen Entities] parms[{"name":"1","value":"Table Tickets"}] ...
2017-11-04 11:35:40.201 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:40.271 [GETDATA] [Entity Screen Entities] parms[{"name":"1","value":"All Tables"}] ...
2017-11-04 11:35:40.272 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:40.276 [GETDATA] [Entity Screen Entities] parms[{"name":"1","value":"Delivery"}] ...
2017-11-04 11:35:40.277 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:40.305 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:40.305 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:40.307 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:40.313 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:40.345 [GETDATA] [Entity Screen Entities] parms[{"name":"1","value":"Customers"}] ...
2017-11-04 11:35:40.345 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:40.345 [GETDATA] [Entity Screen Entities] parms[{"name":"1","value":"Customer Tickets"}] ...
2017-11-04 11:35:40.346 [SQL] Connecting [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] ...
2017-11-04 11:35:40.374 [SQL] Connected [DRIVER={ODBC Driver 13 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=SambaPOS5;] user[sambapos] handle[Resource id #43].
2017-11-04 11:35:40.497 [SQL] Fetched [Entity Screen Entities] records[27].
2017-11-04 11:35:40.589 [SQL] Fetched [Entity Screen Entities] records[60].
2017-11-04 11:35:40.623 [SQL] Fetched [Entity Screen Entities] records[2].
2017-11-04 11:35:40.887 [SQL] Fetched [Entity Screen Entities] records[2].
2017-11-04 11:35:40.914 [SQL] Fetched [Entity Screen Entities] records[57].
2017-11-04 11:35:40.960 [SQL] Fetched [Entity Screen Entities] records[56].

#26

Could we use Trial license to run POS1?
I could run Ticket Explorer, but can not run POS module. It stop at loading


#27

You should use QMX forum for that question.


#28

QMX 1.1.0

download.qmxcode.com/QMXsetup.exe

  • Key Management moved to QMX-Server.

  • Key Registration in QMX Client simplified and automated.

  • Client Logging. Toggle Log Screen using backtick key ( ` )

  • Patch mechanism to facilitate quicker fix patch releases and smaller downloads.

  • Client Modules can be toggled in/out of “fullscreen” using backslash key ( \ ), or by clicking in the bottom-right corner. This hides or shows the top NavBar.


#29

Would like share how you do the CC integration or at least which gateway, network or equipment you have successfully done?


#30

QMX 1.2.0 released (2018-03-17)

For details see the release announcement, or for a summary see the first post.


#31

Spent last two days trying to update to Windows 10 in order to install SQL 2016 so I can finnaly have a play with this but bloody Windows update keeps failing :frowning:


#32

With the payment function added, it reignite my interest. GOOD WORK!


#33

@QMcKay is there plans to support submenus?
Also is it just me or is force potion selection required for portions full stop? selecting order doesnt offer portion choice.


#34

GraphQL query getMenu() does not return data for SubMenus, Custom Commands, nor Automation Command Name/Value, which is why there is currently no support for it. It’s a bit of an oversight IMO.

That said, QMX-Server makes it possible to support a lot of other features that have been implemented in QMX, that the official mobile client is not capable of. I have been seriously considering adding those Menu features for quite some time now, and may do so in the next version.


#35

Look forward to that, was I missing something on the portions?
It seems to need to be set to force portion selection to enable it, ie a product with portions cannot be selected to set portion?


#36

I don’t know what you mean. It follows the autoSelect setting for a Menu Item (in your SambaPOS Menu) to determine whether or not to show the Order Tag Screen (which is where Portions are also displayed).

If you close the Order Tag Screen and then decide you need to make changes, then you click on the Menu Item on the Ticket to show the order Tag Screen again, just like in SambaPOS.

The forcePortionSelection option/setting has no equivalent in SambaPOS (without extra Automation). It simply displays a dialog containing the Portions for selection. If you select the incorrect Portion, then you can click on the Menu Item on the Ticket to show the order Tag Screen (which again, contains the Portions), just like in SambaPOS.


#37

I am guessing he might mean specifying a specific portion for the menu item. So in SambaPOS if you have portions Small, Large you can specify on the menu item you want to use Large as default. I haven’t checked but possibly he is using this and it isn’t being followed in QMX?


#38

Having experimented a little further it would seem portions are not shown on order tag screen if there are no order tags for that product.


#39

QMX obeys the Menu Item settings for autoselect, portion, and default order tags.


#40

Wow, you’re correct. Never had that scenario in my systems. I will fix that pronto.

EDIT: this is only an issue in POS1. POS2 works as it should.


#41

Autoselect option is posibly effected also as my btg wines are autoselect but doesnt show (again no order tags for that products.
There would be on live system but not yet…


#42

Seems to be only POS1 (A) with this issue.

Try POS2 (B) and let me know if it has the same issue.


#43

POSB shows portions in the above senario but autoselect doesnt seem to work for me. Its not an option is it?
Autoselect on product with tag but not on one with just portions.


#44

Also, should order grouping be applied? I understand it might not display on QMX but opening ticket on samba afterwards doesnt show grouping that would be there if rang in in samba.

Although saying that v 6.2.3 seems to have broken the previously working grouping anyway… :frowning: