Overview:

An error continuously occurs with different fields: No such column. The user is granted access to the fields.  When the user is granted Field Level Security (FLS) for field A, the error refers to field B and then field C, etc. 

Root Cause:

Solution:

To resolve the error, follow these steps:

Enable profile access to the Apex Class VeevaUserPermissions:

1. Navigate to: Setup --> App Setup --> Develop --> Apex Class.
2. Select Apex Class VeevaUserPermissions. 
3. Enable profile access to the Apex Class VeevaUserPermissions.
   • Click Security.
   • Select all profiles under Available Profiles. It is important to select all profiles, even if Permission Sets is defined, in order to avoid future configuration inconsistencies.
   • Click Add to move them to Enabled Profiles.
   • Click Save.

Note: It is important to select all profiles, even if Permission Sets is defined, in order to avoid future configuration inconsistencies.

Enable the PermissionSet Support Veeva Custom setting:

1. Navigate to: Setup --> Build --> Develop --> Custom Settings --> Veeva Settings --> Manage.
2. Select the Veeva setting: PermissionSet Support when using Permission Sets. 
3. Clear Veeva Cache after the change is made.

Related Documentation:

• CRM Knowledge Base Article: Error: No such column (Field_vod__c) on entity (Object_vod__c) - When Performing Veeva CRM Synchronization
• CRM Help Documentation: Implementing Security in Veeva CRM