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.
The Apex Class VeevaUserPermissions is not enabled for the user.
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.
CRM Help Documentation: Implementing Security in Veeva CRM
Send us your feedback: We are always looking for feedback to help improve our Knowledge Base! Please let us know if this article is helpful or provide feedback on how we can improve your experience by clicking here.