mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-10-07 23:56:56 +01:00
0120b874b2
- release-must-update-app-version.md: reframe around AppSource's actual
strict full-version-ordering requirement; scope branching-policy
claims as team convention, not platform rule.
- pictures-must-use-media-not-blob.md: MediaSet is a collection of
independent media objects, not automatic image variants/thumbnails.
- log-writes-must-survive-rollback.{md,good.al}: StartSession's only
data channel into the new session is its Record parameter to a
TableNo-scoped codeunit; a setter called on a local instance before
starting the session populates nothing in the new session.
- exposed-objects-must-be-in-a-permission-set.md: correct the three
exposure mechanisms (Web Services config, PageType/QueryType=API,
ServiceEnabled as a method-only attribute).
- pages-must-not-contain-business-logic.md: scope to persisted
mutations and cross-entry-point rules; presentation-only
calculations and table-owned invariants are not violations.
- given-blocks-must-cover-full-precondition-chain.good.al: replace
invented LibrarySales calls with the real API
(CreateCustomer/CreateSalesOrderForCustomerNo/PostSalesDocument).
- test-feature-scenario-tags.{md,good.al}: move [SCENARIO] inside the
test procedure body to match the current BCApps corpus; keep
[FEATURE] at codeunit level per Microsoft's own documented option.
- ui-test-codeunit-naming.md: scope the _UT suffix and adjacent-ID
pairing as an explicit team convention, not a BCApps-wide standard.
- page-design-must-match-bc-page-type-conventions.md /
table-design-must-match-bc-table-type-conventions.md: Card's
single-key primary-key claim is a contextual heuristic, not a
mandatory constraint (Ship-to Address, Customer/Vendor Bank Account
are real composite-key Card pages); a Subsidiary table with its own
identity commonly gets List+Card, not Worksheet/Tabular.
- api-page-least-privilege-write-access.{md,good.al}: only page-placed
fields are ever exposed; set InsertAllowed/DeleteAllowed=false in the
good sample so a narrow field set can't still create/delete records.
- source-organized-by-feature-not-object-type.md,
test-one-when-per-test.md: scope as team/testing-design conventions,
not Microsoft platform requirements.
- upgrade-tag-logic-must-not-nest-deeply.md: add the Microsoft Learn
citation that already backs the two-level nesting limit.
- Wire the new articles into the testing/data-modeling/error-handling/
security/ui review skills' candidate-selection signals.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
49 lines
2 KiB
Markdown
49 lines
2 KiB
Markdown
---
|
|
bc-version: [all]
|
|
domain: data-modeling
|
|
keywords: [blob, media, mediaset, picture-field, image-field, table-design]
|
|
technologies: [al]
|
|
countries: [w1]
|
|
application-area: [all]
|
|
---
|
|
|
|
# Pictures must be stored in a Media/MediaSet field, not BLOB
|
|
|
|
## Description
|
|
|
|
`BLOB` is still a valid AL field type for arbitrary binary data, but it is
|
|
not the right choice for storing pictures or images. The current
|
|
recommendation is the `Media` field type for a single image, or
|
|
`MediaSet` when a record needs several independent images (e.g. multiple
|
|
product photos) — `MediaSet` is a collection of separately-imported media
|
|
objects, each with its own identity; it does not generate resized variants
|
|
or thumbnails on its own, and displaying more than one item still requires
|
|
custom page handling. Media/MediaSet integrate with the platform's
|
|
picture control and media repository, which a plain `BLOB` field does not
|
|
— but any derived preview or thumbnail image still has to be generated
|
|
explicitly and stored in its own field, regardless of which type holds the
|
|
source image.
|
|
|
|
`BLOB` remains the correct choice for genuinely arbitrary binary payloads
|
|
that are not images and don't benefit from the media pipeline (e.g. a raw
|
|
file attachment blob unrelated to picture rendering).
|
|
|
|
## Best Practice
|
|
|
|
Use `Media` (or `MediaSet` for multiple image variants) for any field that
|
|
holds a picture.
|
|
|
|
See sample: `pictures-must-use-media-not-blob.good.al`.
|
|
|
|
## Anti Pattern
|
|
|
|
A `BLOB` field named "Picture" compiles and stores the image bytes, but
|
|
it misses the picture control integration and media repository that a
|
|
`Media`/`MediaSet` field provides for free — the anti pattern is choosing
|
|
`BLOB` for image storage out of habit rather than recognizing that the
|
|
field is holding a picture, not generic binary data. A related anti
|
|
pattern: assuming `MediaSet` gives automatic image variants or thumbnails
|
|
because it sounds like a collection with derived versions — it is only a
|
|
collection of independently-imported media objects.
|
|
|
|
See sample: `pictures-must-use-media-not-blob.bad.al`.
|