It’s not a SambaPOS issue the system is working as intended. You may make a feature request but it’s unlikely v5 will get more updates. You can rename them to something that truncates them to end.
He is working on the next version but it will be a while before we see anything. SambaPOS the company is making a lot of changes to how it does business. The forum is no longer it’s source of communication as far as features or even support is concerned. I think they are moving into more traditional pos realm and away from forum. I could be wrong though.
Wow that is bad. Unless they can write up user manual but then it will be less flexibility. I’ve been using SambaPOS since v2.9 I like it because it has active forum.
You could open the database through SQL Management Studio, and inside the Table Payments, you could run an update query to change the UserID to an existing users’ id, and then try deleting the old users.
I know it can be done but assign to another user doesn’t sound right (maybe he/she not even work there yet). What is Kendash suggest it most logical for me too.
So, @na1978 I think you probably have too many users on the screen. I don’t know if you use entity screen for that (I think you do otherwise 300 users should not bother you if it assign to ticket by {:CURRENTUSER} ). You may assign old users entity state to Inactive and current users to Active entity screen State Filter to Active.
You will most certainly corrupt or even crash your system if you manually edit the SQL like that. Entities were not meant to be deleted if assigned to transactions. There are multiple tables and entries that interact with them so manually editing is not smart.
Surely you can just rename them after so long… I usually prefix or suffix old users for 4-6months then once I cant remember who they really were I rename them.
After 6 months of them being left its unlikely any queries will be resolvable on the basis of who the user was.