Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Chris Harrison]

Hello,

We are using the out of the box Job card terminal to perform production transactions in D365.  We are not performing HR/Payroll in D365, so we have setup batch jobs to process our Calculate/Approve/Transfer Time & Attendance registrations.  The problem we are encountering is we sometimes run across workers who have not been clocked out for a given profile date, which causes some of our batch jobs to fail.  To try and fix this, we have attempted to run Clock out workers (Time and attendance > manage registrations > Clock out workers) as a batch job as well.  From reading through the D365/AX documentation, it looks like Microsoft has mentioned this can run in batch.  The problem is, it doesn’t seem to work.  We’ve tried running the job with no Profile date set in the parameters, along with setting a Profile date.  When set with a Profile date it will clock workers out for that date, but come the next date it no longer works.

So before I look to make some tweaks to the Clock out workers job, I’m curious if anyone has got this to run in batch and if so, what setup am I missing?

We are on D365 10.0.12 Update 36.

Thanks!

——————————
Chris Harrison
IT Integration Manager
Fort Wayne Metals
Fort Wayne IN
——————————

[Soren Normann Rasmussen]

Hi Chris,
you might need to use a dynamics date to get the batch to pickup the date correctly.
My experience is when the date field is left blank, that the batch job will keep using the date, from when the batch was added to the batch que.
If you go into that batch job and look up the parameters it would probably have a fixed date in there from where the batch job was applied.

Below are my notes from when I had a similar problem, it might be worth testing out.
I hope this helps.

(Below some examples, you can use this in query’s so you can use them in recurring batches without the need to change it daily. Give it a try in a testenvironment to see if it meets your requirements. Simply key in the bold statement below in a datefield. In your case it would be (greaterThanDate(1)).

• (dayRange(-30,0)) – Results in a date range for the last 30 days: “26-01-2014”..”25-02-2014″
• (day(-1)) – Results in yesterday’s date: 24-02-2014
• (day(0)) – Results in today’s date: 25-02-2014
• (day(1)) – Results in tomorrow’s date: 26-02-2014
• (greaterThanDate(2)) – Results in every date after today plus 2: > 27-02-2014
• (lessThanDate(-1)) – Results in every date of today minus 1: < 24-02-2014
• (monthRange(0,2)) – Results in first day till the last day of the month’s choosen (0 = current month): “01-02-2014″..”30-04-2014”. (monthRange(-1,-1)) will give you previous month.
• (yearRange(-1,-1)) – Results in first day till the last day of the chosen year: “01-01-2013”..”31-12-2013″

——————————
Soren Normann Rasmussen
SSS Australia
Murarrie
——————————
——————————————-

[Chris Harrison]

Hi Soren,

Thank you for the response.  Yeah, I’ve used your method when setting up a batch job and setting date filters.  It works great as you mention.  However, this is a parameter date option for the Profile date, not a filter field.  So when I try to use these date methods I get an error that says “(day(0)) is not a valid Date. Please enter date in M/D/YYYY format.”.  So unfortunately I don’t think this will work.  Thanks for the suggestion though, it’s appreciated.

Chris

——————————
Chris Harrison
IT Integration Manager
Fort Wayne Metals
Fort Wayne IN
——————————
——————————————-

[Kristina Dummermuth]

If you go into the Item master page and click on the Sales tab, you will see a place where you can put in an External Item Description.

 

I use this on the PO side, so the Vendor’s information shows up on the PO when It is generated. You can put their customer #, their PO # and the part description. It works wonders.

 

I hope this helps..

 

Kristina Dummermuth
Spare Parts Specialist
 

Frontmatec inc 8301 N.W. 101st Terrace #10 Kansas City, MO 64153  United States frontmatec.com	Fax : Email:	+1 816 891 0550 kdu@frontmatec.com

 

——————————————-

[Jonathan Howe]

I have never tried to run in batch but run it regularly interactively and have found it an infuriating process. Firstly I think you must have a profile date for it to do anything useful. Second, I find that it often throws errors, particularly if workers are still in progress on a production job. It is not always the case and I cannot determine precisely which scenarios cause the clock out to fail. In this scenario we have to impersonate the user and use the Job Card Terminal to perform a clock out.

We are using calculate and transfer to payroll so we only use the clock out workers occasionally e.g. around public holidays, to get a nice clean system.

——————————
Jonathan Howe
IT Manager
Cross Manufacturing
Bath, UK
——————————
——————————————-

[Chris Harrison]

Hi Jonathan,

Thanks for the response.  Yeah, I’m agreeing with you…I think you do have to have a profile date.  I’m just confused why in the Microsoft documentation it says this job can be run in batch.  This caused me to believe it’s something that could be scheduled, but I’m beginning to think they were just saying you could run the job local or in batch for a given profile date.  OK, I’m thinking I’m going to have to do some sort of tweak to this job to make it work as a scheduled batch job.  Thanks for the thoughts.  It’s appreciated.

Chris

——————————
Chris Harrison
IT Integration Manager
Fort Wayne Metals
Fort Wayne IN
——————————
——————————————-