• Kevin Ridley
  • NEWBIE
  • 0 Points
  • Member since 2019

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 2
    Questions
  • 5
    Replies
I'm trying to use the chatter/feed-elements api.  I'm trying to follow the documentation from v35 because I need to attach the file to an opportunity (subject_id), and later versions removed this ability I believe.  Anyway, the documentation doesn't really say how to encode the binary data.  The example shows the following: Content-Type: application/octet-stream; charset=ISO-8859-1.  My client app is reading a file into a blob with UTF-8 encoding and uploading through the API.  I get a 201 return and the file gets uploaded to the correct opportunity, but the size is not right, and you cannot preview or open the file.  I don't think I can get my client app to pass ISO8859-1 (and WHY would SF use tha tinstead of UTF-8 anyway???), so what are my options?  Can we configure the instance to use UTF-8 instead?  I tried changing the value in the request to tell it I'm passing UTF-8 and I get the same results.
SF beginner here.  Ive been setup with a sandbox to work in their lightning.force.com environment.  I'm trying to obtain an access token using a windows app via http.  First thing I did was create a connected app.  I have it setup for OAuth and saved the Consumer Key and Secret codes.  When I try to use the password flow to get an access token, I get an invalid_client_identifier.  I have checked the value and it's correct.  I'm thinking it must be some sort of permission issue.  Do I have to use an endpoint in my sandbox, or do I use the documented https://login.salesforce.com/services/oauth2/token ?  Any other thoughts?
I'm trying to use the chatter/feed-elements api.  I'm trying to follow the documentation from v35 because I need to attach the file to an opportunity (subject_id), and later versions removed this ability I believe.  Anyway, the documentation doesn't really say how to encode the binary data.  The example shows the following: Content-Type: application/octet-stream; charset=ISO-8859-1.  My client app is reading a file into a blob with UTF-8 encoding and uploading through the API.  I get a 201 return and the file gets uploaded to the correct opportunity, but the size is not right, and you cannot preview or open the file.  I don't think I can get my client app to pass ISO8859-1 (and WHY would SF use tha tinstead of UTF-8 anyway???), so what are my options?  Can we configure the instance to use UTF-8 instead?  I tried changing the value in the request to tell it I'm passing UTF-8 and I get the same results.
Hi - I'm getting this error in Salesforce when trying to access documents in Sharepoint, "External Object Error OAuth token expired." I've tried getting in contact with Sharepoint support but they told me to contact Salesforce, and we don't have the premium support for developer support from Salesforce.  

Name items_Sharepoint
External Data Source Sharepoint
Status OAuth token expired

Does anyone have experience with Sharepoint and refreshing a security token? I've tried to go through documentation but I'm having trouble getting the connection working again.  

I can see sharepoint in our external data sources as well as Auth. Providers.  
 
SF beginner here.  Ive been setup with a sandbox to work in their lightning.force.com environment.  I'm trying to obtain an access token using a windows app via http.  First thing I did was create a connected app.  I have it setup for OAuth and saved the Consumer Key and Secret codes.  When I try to use the password flow to get an access token, I get an invalid_client_identifier.  I have checked the value and it's correct.  I'm thinking it must be some sort of permission issue.  Do I have to use an endpoint in my sandbox, or do I use the documented https://login.salesforce.com/services/oauth2/token ?  Any other thoughts?