Error 350 When Sending File

  • 1
  • Problem
  • Updated 2 years ago
I have an integration that essentially will take a file from a list, create a folder in the SF user's "Personal Files" area, upload the file, and then send it out to an email recipient via SF. This has worked without issue in many different SF domains, however in this particular domain, I get the following reponse back:

ShareFileResponse><error>True</error><errorMessage>NOTFOUND: Insufficient access</errorMessage><errorCode>350</errorCode></ShareFileResponse> 

The user appears to have access and can create both folders and upload files to the personal area when logged in via the web portal. I can't see any security settings that would prevent this.

Can anyone nudge me in the right direction with this one?
Photo of worldox


  • 1 Post
  • 0 Reply Likes

Posted 2 years ago

  • 1

Be the first to post a reply!