Client post function fix #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using correct json_encode arguments. getParams breaks because it isn't JSON.
Using correct json_encode arguments. getParams breaks because it isn't JSON.
|
Thanks for the patch. I haven't been using Salesforce for some time now so I don't know if anything has changed. Can you find anything in their docs? |
|
Actually no. It MAY actually have more to do with the fact that you're not locking the version of Guzzle actually. I'm not 100% sure because I don't know what version of Guzzle you were originally using. http://www.salesforce.com/us/developer/docs/apexcode/Content/apex_rest_code_sample_basic.htm After looking at the URL above it's pretty clear that it expects application/json content in the body when creating or requesting (in my case tokens) accounts, so I used that to force the post to use json in the body. This worked. Again, not really sure if Guzzle or Salesforce. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I discovered that the reason that this function was broken was because Salesforce expected a json array of arguments. This is provisional - maybe this is because it's a new version of their API?