we get the error when user try to use drag and drop - Unexpected error: ERROR DETAILS ex= Code: INSUFFICIENT_PERMISSION Details: You do not have permission to perform this operation. Details: You do not have permission to perform this operation. Code: INSUFFICIENT_PERMISSION Id: StackTrace: [Ljava.lang.String;@3e3c307c User event: null Internal Id: null Type: nlobjError - how to solve?

AI generated answer (using internal Slack threads):

The error message you're encountering,

INSUFFICIENT_PERMISSION

, indicates that the user role doesn't have the necessary permissions to perform the operation. Here are some steps you can take to resolve this issue: 1. Check the User's Role Permissions: Ensure that the user's role has at least Edit level of Document and Files Permission under the lists subtab. If it's set to 'Create', try updating it to 'Edit'. 2. Check Folder Restrictions: Verify if the folder where you're trying to drag and drop files has any restrictions. If the folder is restricted to a certain group of people or marked as private, it might prevent certain roles from performing operations. 3. Check Record Permissions: If the issue persists, check if the user has the necessary permissions on the records they're trying to interact with. For instance, if they're trying to attach files to a customer or supplier record, they should have at least 'View' permission on customers and suppliers. 4. Check Custom Records Permissions: If you're using custom records, ensure that the user's role has the necessary permissions to interact with these records. 5. Check Track Messages Permission: This permission allows viewing and editing of the Message record. Make sure the user's role has this permission set to 'Edit'. 6. Check Notes Sublist Permission: The Notes Sublist permission is required for the drag and drop functionality to work properly. Also, the Notes Sublist needs to be visible on the form. Remember, changes to permissions might take a while to propagate, so you might need to wait a bit before testing again. If the issue persists, it might be a good idea to clone the role and try adjusting permissions on the cloned role to identify the issue. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******