-
Notifications
You must be signed in to change notification settings - Fork 430
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,7 +10,6 @@ using Microsoft.Finance.GeneralLedger.Ledger; | |
| table 6845 "Spend Request To G/L Link" | ||
| { | ||
| Caption = 'Spend Request To G/L Link'; | ||
| ReplicateData = false; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This PR's sole change is removing Recommendation:
👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.31.4 |
||
| DataClassification = CustomerContent; | ||
| LookupPageId = "Spend Request To G/L Link"; | ||
| DrillDownPageId = "Spend Request To G/L Link"; | ||
|
|
||
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