{Start} : replaced with Workperiod Start date/time
{End} : replaced with Workperiod End date/time
@1 : replaced with first parameter from Report, which is Employee
@2 : replaced with second parameter from Report, which is Daniel B.
So I can only guess, but what I would try at the very least, one at a time until it works:
Ensure your Entity Type is called Employee.
Ensure you have started a Workperiod at least once. If you have no Workperiods, the report will fail. You do not need to be within a Workperiod to see the report, but at least 1 Workperiod must have existed in the past.
Try replacing in the SQL Script (the single quotes are mandatory):
I notice after the 8th hour of each day, the employee gets OT hours. How do I configure it so that the employee gets OT hours after the 40th HOUR of each WEEK?
Will I be able to fit 20 or more employee widgets on this screen? The space seems limited. I guess I’ll just remove the Reports Widget and leave only the Entity Grid Widgets.
In emre’s post, in the link above, there is a button for “Break”. How do I implement that into the reports?
How do I CLEAR the SQL data for the Time Clock?
How do I EDIT the SQL data for the Time Clock?
Let’s say an employee forgot to Clock Out at the end of his or her shift, or there was a problem and an employee could not Clock In.
You need to change the SQL to calculate it in this way. You will also need to be specific as to what a “week” is - which day it starts and which day it ends.
Not likely, and the performance for pulling even just 4 Reports can be slow. You could have a single Report, and use automation to load the report for the chosen employee via click of Automation Button, Entity Button, or Entity Grid. I have the Punch Editor and Payroll setups operating this way.
With more automation, similar to above.
Run SQL script in SSMS…
DELETE FROM [EntityStateLogs]
Install the Punch Editor setup. Part of this Tutorial:
That said, there does not appear to be a stand-alone Tutorial for the Punch Editor. Kendash has put the Timeclock and PunchEditor into a Configuration Task instead… and you may not like the way his Timeclock is set up, since it is quite a different flow. Proceed with caution. I will try to find some time to create a Punch Editor Tutorial.
No worries. But each of these should be taken 1 at a time, and you should make separate topics for them.
@rightguys Ok sorry it was late but if you add this to your Configuration Repository URL’s section in Settings > Local Settings > Online Services it will give you the Punch Editor Configuration Task.
I want to thank you for such a comprehensive walk through of this module. Truly a great assistance . If you have any other Modules to share I would be very grateful. I have struggled to setup some elements up but this walk through has given me a better understanding of setup.
Thank you very much for support and you are a asset to this forum.
Hi guys, This looks ace - thank you for sharing. Is there a canned version of this available as a DB Tools import file, can’t seem to find it in the post?
Im not sure if there was but setups like these are normally reluctant to share db tool import as they ALWAYS follow with an onslaught of questions from people which just install and them mess it up as haven’t taken the time to learn how the setup was done.
*** I think it should be @@EmployeePunchInLatest. Upper case I. Emre noticed a typo in comments below and I had the same typo, since I cut and paste I thought I should check tutorial. Its incorrect above in the body of the tutorial. I couldn’t place it where the actual error is. I can explain it better if you can not locate the error. Thanks
This is really frustrating. I have a staging environment where I’ve followed this tutorial and the time clock works, INSERTing records into the [EntityStateLogs] table. However, in our production environment, I have the exact set-up, but only see UPDATES for [EntityStateValues].
I’ve numerously checked my TC_LogEntityState Action and Rule, but completely unable to find the reasons why. Can someone help me please?
We can only guess what is wrong. You need to provide screenshots of your setup for us to help.Right now based off what you have told us there is a 50/50 chance a moose has sat on your other till causing the issue… but I cant be certain…