The Table Relations Metadata mapping of where(...) filters to
Condition Field No. is not documented and could not be verified; the
rule does not depend on it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- tablerelation: fields with ValidateTableRelation/TestTableRelation = false
are skipped by codeunit 134926 and may be longer (filter/totaling
fields); shorter is still a finding. Add Code/Text type rule, BaseApp
evidence, a ValidateTableRelation = false filter field to the good
fixture, and the carve-out to the data-modeling cue.
- recordref: add FindLast/Next, relabel SplitLocalTableFilter as filter
splitting, mark fixtures as test-library-style helpers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- data-modeling: tablerelation-field-length-must-match-related-field
(exact length for unconditional relations, at least the longest target
when all relations are conditional; no compile-time diagnostic)
- testing: recordref-open-temp-parameter-defeats-real-table-checks
(a temp-opened RecordRef is empty, so existence/uniqueness checks on it
never see persisted rows; cross-links use-generateguid article)
- Wire both into the review leaves and register the fixture pairs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
