Nothing changed. iPhone 6 running iOS10.2. Replicon app updated 1/16 latest release. Receive the error below only when trying access timesheet approvals from the dashboard. No error on time off approvals.
Error - You do not have access to perform this operation. Please refresh your app data.
Error - You do not have access to perform this operation. Please refresh your app data.
Posted 1 year ago
_large.jpg)
Raghu K, Community Moderator
No. refresh app data does not correct the issue, just send you back to your own timesheet. Error also happens when trying to view previous timesheet approvals. Log file to be sent momentarily.
Raghu K, Community Moderator
Thanks, we shall review the logs and contact you.
Timesheet can be approved if not opened. Error only occurs when try to open/view the timesheet.
Raghu K, Community Moderator
Thanks again, we have identified the problem and shall have this addressed soon.
Sorry for the inconvenience caused to you.
Sorry for the inconvenience caused to you.
Raghu K, Community Moderator
An update!
We are currently in process of submitting a new app into App store to address this issue. Shall update this post once it's made available for download.
Meanwhile, you can apply the below workaround to address the situation:
Enable Time Punches view access under the supervisor permission set, details steps are below:
We are currently in process of submitting a new app into App store to address this issue. Shall update this post once it's made available for download.
Meanwhile, you can apply the below workaround to address the situation:
Enable Time Punches view access under the supervisor permission set, details steps are below:
- Navigate to Administration and then permission sets
- Open the supervisor type permission from the list
- Check "View" access for Time Punches option
- Save the changes
(Edited)
Thanks. Fixed applied.
For what it's worth, here is a screenshot from 1 year ago when the exact same fix was applied for another bumbled update from devs. Pass that along to them.
For what it's worth, here is a screenshot from 1 year ago when the exact same fix was applied for another bumbled update from devs. Pass that along to them.