Timesheets
Expand | ||
---|---|---|
| ||
Answer: The first thing to check is, in Workbench, are there duplicate contact records for the same person? If so, the time usually is going into Workbench however it's syncing against the non-employee personId (Same Name but inactive or supplier contact). This means that the costs on the Job will appear and show $0 (no employee class on non-employee person record). Prevention:
Remediation:
Integration Enhancements: We have made some updates recently to improve the integration to more accurately match the data for employee timesheets. We now validate:
This should address most of these issues where you may have an employee who works part time and is listed as a supplier contact, as well as duplication of contact records (multiple contact records for the same employee, inactive and active). See release notes: 4.5.40 - 24 Oct 2022 If you have this issue, please check the above and escalate to support if you need assistance. |
...
Expand | ||
---|---|---|
| ||
No, we do not currently support duplication of the daily diaryThe duplication function was introduced in the Daily diary in March 2023. If your diary is older than this, you will not be able to duplicate diaries without causing issues to your transactional data. Where a daily diary has been duplicated, the associated transactions remain linked to the original diary, therefore new timeslots cannot be generated in Upvise. A new diary must be created to ensure the transactions generate as expected and land in workbench seamlessly. To receive this enhancement on your site, please contact your consultant or Workbench Support to arrange an estimate for your Daily Diary migration & install. |
User configuration
Expand | ||
---|---|---|
| ||
Removing an application on an individual user not only hides the app from showing in their menu, it also removes their ability to access the functions of that app. Example: if you turn off "Forms" in individual user application rights in Upvise, this means the user won't be able to create any forms across the entire database. The user will be presented with an error that looks like this when they try to ('ReferenceError: Can’t find variable: Forms CODE:' A solution to this is:
You can use the same logic across all apps. |
...