Dont Delete Entities which are not in data.xml file #316
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 Wael, We are using your extract config migration data task in Azure Devops pipeline. I observe that you are deleting the entities data which are not there in data.xml file. Can you comment these particular lines as we need all the entities data xml files which are created prior to the execution of the current even though the entity is not present in the data.xml file which is be exported using CMT tool. We are using this task and pushing the changes to our github for tracking of the files or entities xml's. So , by commenting these lines we will be able to retain the files and can use for source tracking inside our GitHub. Need your help in this scenario. If you have any other option to avoid deleting the previous files using your tasks, that's also fine for us to proceed. Thank you.
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.
Hi Wael,
We are using your extract config migration data task in Azure Devops pipeline. I observe that you are deleting the entities data which are not there in data.xml file. Can you comment these particular lines as we need all the entities data xml files which are created prior to the execution of the current even though the entity is not present in the data.xml file which is be exported using CMT tool. We are using this task and pushing the changes to our github for tracking of the files or entities xml's. So , by commenting these lines we will be able to retain the files and can use for source tracking inside our GitHub.
Need your help in this scenario.
If you have any other option to avoid deleting the previous files using your tasks, that's also fine for us to proceed.
Thank you.