Are you using SQL express 2017? Actually nm that shouldn’t matter. Hmm it’s gotta be a simple typo
Are you using beta 5.2.23? That is required.
Yep. I just downloaded the latest Beta version. Currently shows Beta 114.
Currently using SQL 2017 express as well
Does the code match what you have in your current script?
Try taking the sales script out for now. Your on 5.2.23 right?
Im pretty certain i am.
Am i meant to type something specific in the bar next to the Test button?
I removed the sales part but still gives me a syntax error.
I double checked the whole code to ensure im not missing any ‘;’ and can confirm they are all there.
Weird
Is the code you have in your tutorial the updated one I can maybe try?
If you try to punch in it doesn’t work?
Do the names also have to match? or are the punches the only Unique thing that has to match in Samba and in 7shift?
That wouldn’t matter. One second I had to go to restaurant. I’m heading back.
Ok i am back let me test some things.
OK So if I just type 7shifts in the test parameter I get the same thing but thats because it needs a full function. Likely its working fine… Try this.
in the test box type:
punch('944','clocked_in','2019-08-01 11:50:00')
Replace 944 with an employees pin and replace the time with local time for you.
If that works and you get a punch then we need to look at the script action.
Also did you install it after installing the time clock or did you install time clock after installing my dbtools file?
Ok so i did this and i got a syntax error
I installed time clock after the file in this topic. Hmm do you think that could be the reason?
Yes that messes it all up. I actually modified things in the Entity screens and a couple of the actions and even renamed them. My file works without the time clock.
However the script should work so let me look closer.
In 7 shifts for employee you set the PUNCH ID as user pin … not employee id correct? We actually are not using Employee ID at all just punch id.
Its under Employee > HR/Payroll then Punch ID