Overview:
A user tries to edit an Account, but receives the following error message after clicking on the Edit button: No Account returned for ID: [Account ID].
Clearing the Veeva Cache resolves the issue, but only for a few minutes.
Root Cause:
The Apex Class VeevaUserPermissions is not enabled for the user.
Solution:
The VeevaUserPermissions Apex class needs to be enabled to all user profiles if the Org uses Permission Sets. Not having it enabled may cause unpredictable internal caching behavior.
Related Documentation:
CRM Help Documentation: Permission Sets