You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was using this for a project and noticed that Salesforce expects a map[string]string instead of map[string][]string for the httpHeaders field in composite subrequests.
…stead of map[string][]string
Fixes Issue g8rswimmer#56
A drawback of this fix is, if the user passes in multiple values for a key, Salesforce would still return an error.
Another possible fix is to change the type of Subrequester.HTTPHeaders from http.Header to map[string]string but we probably don't want to do that because callers may expect to be able to pass in a http.Header type for that field.
I was using this for a project and noticed that Salesforce expects a
map[string]string
instead ofmap[string][]string
for thehttpHeaders
field in composite subrequests.https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_composite_record_manipulation.htm
When I use
I get the error
and the request works when I use
The text was updated successfully, but these errors were encountered: