Skip to content

Conversation

@hamiltonkibbe
Copy link

I noticed this library was generating requests to the soon-to-be-retired version 7 API, in spite of what the default api_version would have had me believe. I can open an issue if needed but i hope the description here makes the bug clear:

The login URL should not include the leading v in the api version, just the numeric part.

(See docs at: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_login.htm)

Including the leading v (as is the default behavior with the value "v29.0" results in salesforce returning a server_url with a version of 7.0, which is being retired early next year. I've opted to leave the default value as is, to avoid changing the library's interface, and just to change the implementation to generate the correct URL.

The login URL should not include the leading v in the api version, just the numeric part. 

(See docs at: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_calls_login.htm)

Including the leading v (as is the default behavior with the value "v29.0" results in salesforce returning a server_url with a version 7.0, which  is being retired early next year. I've opted to leave the default value as is,  to avoid changing the library's interface, and just to change the implementation to generate the correct URL.
@hamiltonkibbe
Copy link
Author

Also wanted to share a workaround, which is to explicitly pass a valid api_version without the leading 'v' to the Connection constructor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant