We have hit an annoying window -- a time between releases, when some sandboxes are on v44.0 and some on v45.0, and the production orgs are on v44.0. This happens in every release cycle.
In trying to test open soqlx://{domain}/sid/{sessionId}, on one of my v44.0 sandboxes, I have noticed that it's throwing an exception:
UNSUPPORTED_API_VERSION: Invalid Api version specified on URL
I looked into the code and it's using DEFAULT_API_VERSION in the code
It would be awesome if I could pass an API version on the url like soqlx://{domain}:{apiVersion}/sid/{sessionId} or soqlx://{domain}/v{apiVersion}/sid/{sessionId} or maybe most appropriately, soqlx://{domain}/sid/{sessionId}?apiVersion=v{apiVersion} so I can use this feature in future annoying windows.
We have hit an annoying window -- a time between releases, when some sandboxes are on v44.0 and some on v45.0, and the production orgs are on v44.0. This happens in every release cycle.
In trying to test
open soqlx://{domain}/sid/{sessionId}
, on one of my v44.0 sandboxes, I have noticed that it's throwing an exception:I looked into the code and it's using
DEFAULT_API_VERSION
in the codeIt would be awesome if I could pass an API version on the url like
soqlx://{domain}:{apiVersion}/sid/{sessionId}
orsoqlx://{domain}/v{apiVersion}/sid/{sessionId}
or maybe most appropriately,soqlx://{domain}/sid/{sessionId}?apiVersion=v{apiVersion}
so I can use this feature in future annoying windows.