XrmQuery default API version based on CRM Version#300
Open
Aagaard00 wants to merge 3 commits intodelegateas:gh_masterfrom
Open
XrmQuery default API version based on CRM Version#300Aagaard00 wants to merge 3 commits intodelegateas:gh_masterfrom
Aagaard00 wants to merge 3 commits intodelegateas:gh_masterfrom
Conversation
…e model driven app instead of being hardcoded to 9.2 in the TS "sourcefile" for the XrmQuery JS files
…nBasedOnCRMVersion
mkholt
approved these changes
Aug 23, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Related to issue #245
Changed XrmQuery default API version to be based on CRM Version of the model driven app instead of being hardcoded to 9.2 in the TS "sourcefile" for the XrmQuery JS files
The possible solution i came up with was to replace
with
In
\src\XrmDefinitelyTyped\Resources\dg.xrmquery.web.tswhich the xrmQuery files are generated from. In this way the default api version used is decided by the CRM version of the model driven app where the code is run.Are there any issues with this solution?