Method Community

When we approve Non-Posted Time Tracking (changing Wait For Sync Approval to No), all entries that include break time suddently ignore it. So if person worked 8am - 5 pmwith 60 min break, before updating the Waiting for the Sync Approval they worked 8 hours but after they work 9 hours. Even updating the Duration in the table afterwards changes nothing, it goes back to 9 hours.

Do you know what could the cause be?

Thank you!

Hi There,

I cant think of any reason why this would be happening, but I did have a few more follow up questions for you to get a bit more context here?

First, how are you calculating a break? Are you pausing the Timer and Starting again after the break is complete?

When you say you are changing the Duration in the table, are you changing it on the screen? Or completely Exporting/ Importing the table?

If you are Changing the value on the screen, are you refreshing the grid after saving? The Grid wont refresh on save by default.

This does sound like an unusual one though, I might need to get a support rep to reach out.

Thanks!

Regards,

Ben

Hi,

we actually upload out time entries through MethodAPI and we enter info into the TimeTracking table: TimeStart, TimeEnd and BreakInMinutes. We then calculate the difference between end and start and subtract the break time to find out the duration. It all works fine until we sync with Quickbooks.

When trying to fix the issue, we Update the field in the table (we recalculate the duration again). Afterwards we refresh the grid and it all looks fine until we refresh the grid again.

Thank you!

Hi Again,

Sorry for the late reply. Ive been able to verify this is happening for me too. One thing I noticed when testing is that the field is actually displaying correctly In QuickBooks online, but for whatever reason the data QuickBooks is sending back is always the Gross Duration, rather than the Duration after the break calculation has been applied. Are you seeing this too?

Im going to Log a ticket with our development team to have a look into why this is happening. Ill keep you posted with any updates.

Regards,

-Ben

Hi There,

Ive just heard back from our team that the code fix for this Issue is now live. Are you able to confirm for me that you arent experiencing this issue any longer?

Thanks!

Regards,

Ben

Hi,

sorry for my late reply but so far it looks like the issue has been fixed. Thank you!