-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crmVersion should also set defaultVersion of the API URL #245
Comments
This issue has been raised before. Imo. it should just be updated with each minor update of the API such that XDT by default uses the newest API. Of course this is up to the current maintainers :) |
This strategy does not take into account that there are on-premise users. We do not upgrade immediately. And 9.2 is still unavailable to us even if we wanted to upgrade to it. |
We should be updating the API version already, which I can see is an issue for onprem. |
I looked into this issue while working on an onprem project. The possible solution i came up with was to replace const DefaultApiVersion = "9.2"; with const DefaultApiVersion = Xrm.Utility.getGlobalContext().getVersion().split('.').slice(0, 2).join('.'); In Are there any issues with this solution? |
Right now XrmDefinitelyTyped requires us, as 9.1 users, to call
setVersion
in each form script. But theoretically we already provided our preferred version when generating the definitions with-cv 9.1
argument.I think the defaultVersion of the API should be generated and not hardcoded, does this sound like a good idea?
Thank you!
The text was updated successfully, but these errors were encountered: