Correct Exchange Parser to add parameters in solution and update version #9632
Conversation
This file contains 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
|
Hi there, @nlepagnez We appreciate you sending us the PR. This PR will be reviewed and before December 21, 2023 you will receive an update on the same. |
v-prasadboke
previously approved these changes
Dec 21, 2023
v-prasadboke
approved these changes
Dec 22, 2023
v-atulyadav
approved these changes
Dec 22, 2023
|
Hi @v-prasadboke, @v-atulyadav, thank you for the approval and merge. |
Hi @v-prasadboke, @v-atulyadav is it possible to have your help on this ? |
|
Sorry @nlepagnez, missed your comments here. I'll check the marketplace once |
nlepagnez
deleted the
Correct-Exchange-Parser-For-On-Premises-and-Update-Version
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Required items, please complete
Change(s):
Update Exchange Parser version and correct Parser parameters in Solution
Reason for Change(s):
Bug on solution deployment, parameters default values are not present. The "CreateSolutionv3" script ignore default value of parameters. Issue #9520