Hi Tom! We'll create a defect for this and get it fixed as soon as possible. Thanks!

Diane,

I am running into this issue as well and seems like that the only way to renumber employee is purging all Time Track Activity which is obviously not a solution. Can you please let us know when you expect this to be fixed b/c it seems if anyone is using Time Track they cannot renumber employees without some extra steps of deleting and reimporting Time Track data.

Thanks

We totally understand and apologize for the inconvenience. We are targeting Payroll 2.19.1 which will be available later in January.

Diane - does this also fix the ability to change the status of an employee?  Have a client integrating with Job Cost only (has ADP do their payroll) and they need to change the status of an employee, but have non-job entries in TimeTrack that apparently will never go away.  (Actually, best option here would be to have a way to purge these to history.)

Diane - does this also fix the ability to change the status of an employee?  Have a client integrating with Job Cost only (has ADP do their payroll) and they need to change the status of an employee, but have non-job entries in TimeTrack that apparently will never go away.  (Actually, best option here would be to have a way to purge these to history.)

I believe they added something to fix that in one of the updates.

Ran into that problem early on.   Before the fix was out,  I ended up going out and reinitializing the offending file (which of course only works if everything must be purged).

Edit:  Suddenly realize you are talking about the Status field.  I'm still thinking of renumbering.   I'm not sure if the other patch resolved that or not.

The renumber issue was corrected in PR 2.19.1.  I didn't really find anything on the changing the status specifically but seem to remember something like that fixed in PR 2.18.1 possibly.  I would suggest testing your scenario on PR 2.19.2 or PR 2.19.3 when released in the next week or so.