-
Notifications
You must be signed in to change notification settings - Fork 431
Removed the ReplicateData=false property #10049
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
Open
Bardur Knudsen (BardurKnudsen)
wants to merge
2
commits into
main
Choose a base branch
from
bugs/644864-repl
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR removes
ReplicateData = false;from "Spend Request" (table 6840), "Spend Request Detail" (table 6841), and "Spend Request To G/L Link" (table 6845), and adds all three to the cloud-migration test's expected-table list — enabling OnPrem-to-cloud replication/migration for these tables for the first time. However, most Normal fields in these tables rely solely on the table-levelDataClassification = CustomerContentproperty (e.g. "No.", Type, "Requested By", Status, "G/L Account No.", Purpose, Currency Code, and the various amount/date fields in Spend Request; "Line No.", Description, "Expected Amount" in Spend Request Detail; "Spend Request No.", Amount, "Document No." in Spend Request To G/L Link) instead of an explicit field-levelDataClassification. Per BCQuality privacy guidance, a table-level classification does not satisfy the field-level requirement, and migrated/replicated data should have its destination fields explicitly classified. Now that these tables are newly eligible for cloud migration, the previously low-relevance gap in field-level classification becomes a real privacy/compliance concern for data leaving the OnPrem environment.Knowledge:
👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.31.4