Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 14:46:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Update transferfields-skip-type-mismatch-can-drop-data.md

Browse source
This commit is contained in:
Yahya Touil 2026-08-21 19:04:04 +01:00 • committed by GitHub
parent bb41eed0c5
commit f471bdec20
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
community/knowledge/data-modeling/transferfields-skip-type-mismatch-can-drop-data.md
View file

@ -1,5 +1,5 @@
---
bc-version: [all]
bc-version: [16..]
domain: data-modeling
keywords: [transferfields, skipfieldsnotmatchingtype, type-mismatch, field-mapping, data-transfer]
technologies: [al]
@ -15,7 +15,7 @@ application-area: [all]
## Best Practice
Use `TransferFields(Source)` when matching field definitions are an expected part of the table design. If source and destination fields intentionally have different types, map those fields explicitly and handle the conversion or validation in code. Use `SkipFieldsNotMatchingType = true` only when skipping incompatible fields is an intentional, documented part of the transfer contract.
Use `TransferFields(Source)` only when every field the destination requires, including primary key fields, is guaranteed to share a matching field number and type with the source; this form defaults `InitPrimaryKeyFields` to `true`. Fields with no matching field number, and fields whose types differ across extensions, are skipped regardless of `SkipFieldsNotMatchingType` — that parameter only governs same-extension type mismatches. If the destination depends on a field that falls into either case, map and validate it explicitly in code rather than relying on `TransferFields` to catch the gap. Use `SkipFieldsNotMatchingType = true` only when skipping same-extension type mismatches is an intentional, documented part of the transfer contract.
## Anti Pattern
@ -23,4 +23,4 @@ Using `TransferFields(Source, InitPrimaryKeyFields, true)` as a generic way to m
See sample: `transferfields-skip-type-mismatch-can-drop-data.good.al`.
See sample: `transferfields-skip-type-mismatch-can-drop-data.bad.al`.
See sample: `transferfields-skip-type-mismatch-can-drop-data.bad.al`.