This repository has been archived by the owner on Sep 6, 2023. It is now read-only.
Allow skipping of deletes to be synced to the data lake #13
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Records may be deleted from the BC database for house-keeping purposes. But the data could nevertheless be important and needs to be archived. The following approach demonstrates how you can "customize" the bc2adls extension to NOT delete the same data on the synced data lake WHILE you delete it from Business Central. This is particularly useful for tables like posted documents or entries where records are deleted for the express purpose of archival and not as part of the day to day operations.