Sage 100

I searched the threads but I would not be a good candidate for Jeopardy today. So, with Payroll update 3, is Time Track ready for prime time? Are there still outstanding issues? TIA.

Hard to tell. I have seen a couple of error messages pop up, but when I tried to recreate, nada. I have no one using it yet. ALSO, the MOBILE version will be via MD's ONLY - Sage is releasing the API, but not an actual mobile version themselves.

I have two issues @JaneCavanaugh with Time Track. One is a show stopper for me and another is an inconvenience: 1) When a user enters time through Time Track, the entry gets assigned sequence number 000001. If you enter another time entry for the same employee and date, it also gets assigned the same sequence number 000001 and OVERWRITES the original entry. We found it when trying to ""fix"" time entries. 2) When posting Time Track entries into Job cost, there is a setting in options that allows user to select what type of info posts into the Job Cost comment field. Options are Dept NO+EE No; EE first initial + Last Name; OR EE First name and Last Initial. No matter what you choose, you get Dept No + EE No. Both have been reported to Sage and identified them as bugs. Comment fix is slated for PU4 release in December. No response on sequence number overwriting.

@CooperBlack - I can't replicate the seq issue. I'm in TT Entry and adding more lines, same date, and the seq is increasing. Was this a Punch In/Out originally?

Enter a time entry and post to JC. Then enter another entry for same employee and date.

No. Not a punch in punch out. Our scenario is that the time entry was entered and the time updated to JC or PR. Once that happens, and another time entry it done, the sequence is set to 00001. I agree that if you enter two entries on one day and they are not updated, it acts correctly.

Any word on the mobile time track that was targeted for June 2018 on the road map earlier this year?

See my earlier entry - the MOBILE version will be via MD's ONLY - Sage is releasing the API, but not an actual mobile version themselves. So the timing will then depend on the MD's after they get the API (I think they may actually already have it).

@BethBowers Well that is depressing. The road ahead said they were releasing Time Track Mobile. They didn't mention the part about it wouldn't be usable until an MD wrote a UI.

@DougHiggs - I was a little droopy over that, myself.

I know that the salary equalization utility won't be available until at least March 2019.

@BethBowers @DougHiggs - do you really want a mobile app that will be stuck at version 0.1beta for the next ten years?

Good point Phil.

Sage KB on Sequence number bug - [here](https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=92758&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=3091&cmd=displayKC&dialogID=146036&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true)

Well.. regarding this MD I haven't been able to get my hands on any Time Track Mobile API documentation. Not sure if there is any.... Emailed Sage R & D this morning and the response was ""not sure where its at & will need to follow up with you on that"". So we'll see

@WayneSchulz Thanks for posting the KB article. Now let's see if Sage can fix the problem. they already have the code in the Bank Rec module and other places. I am not a programmer but it should be an easy copy/paste rather than a full re-write. Wishful thinking.