Support » Plugin: Dynamic Time » Approving on Month 1 disabled time entry on Month 2

  • Version 3.4.5.

    Example: A user completes their timesheet for the month of May 2019 and clicks Submit while viewing the May month (let’s say this happens on June 2, 2019). Then the admin reviews and clicks Approve on June 3, 2019 also while viewing the May month.

    Issue: When this happens, the June 2019 month for that user is not editable and the month says that it was Approved on June 3, 2019.

    None of the above actions took place on the June month, so why would the June month be non-editable?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Rhett

    (@rermis)

    Hi Dan,

    There are many explanations, but since I don’t have access to your system I’ll provide a short checklist.

    1) Make sure you’re using a modern browser (Chrome, Firefox, Edge) not Internet Explorer
    2) Ensure the same time period and weeks are identical between the time period the user submitted, and the time period that’s being approved.
    3) If all fails, reverse all timestamps for the period, and resubmit.

    Let me know if there’s anything else I can do to help.

    1) Make sure you’re using a modern browser (Chrome, Firefox, Edge) not Internet Explorer [Dan] I am always using Chrome, nothing else.
    2) Ensure the same time period and weeks are identical between the time period the user submitted, and the time period that’s being approved. [Dan] Our users are always submitting their hours for an entire month, never differently.
    3) If all fails, reverse all timestamps for the period, and resubmit. [DH] This doesn’t seem like a solution. We should be able to “Approve” and then mark as “Processed” for a given month, and not have to reset that as resetting removes those records. If I’m approving and processing the month of May on June 5th, I shouldn’t have to go back and reset the time period so the user can now enter hours for the month of June. This would remove the records and timestamps of when the approval and processing for May took place.

    I can reproduce this over and over.

    Plugin Author Rhett

    (@rermis)

    Hi Dan,

    The reason I proposed resolution #3 is because this will usually correct any inconsistencies in the database for the time period at hand. It will not be an action that you would have to perform for every time period.

    For more personalized troubleshooting, please follow the “Support & Diagnostics” menu item at the top right of your Dynamic Time Admin page.

    But resetting is something I’ve had to do every month. This isn’t the first and only time I’ve had this issue.

    Plugin Author Rhett

    (@rermis)

    Understood. If you are able to provide the diagnostics I will be happy to continue troubleshooting this issue for you.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.