Skip to content

docs(PC0036): describe SetRecord as positioning and document the temporary-source exceptions - #225

Merged
Arthurvdv merged 1 commit into
mainfrom
docs/pc0036-setrecord-positioning
Nov 17, 2026
Merged

Arthurvdv merged 1 commit into
mainfrom
docs/pc0036-setrecord-positioning

Conversation

@Arthurvdv

Copy link
Copy Markdown
Member

Summary

Companion to ALCops/Analyzers#643 (issue ALCops/Analyzers#368). PC0036 now reports a temporary record passed to Page.SetRecord() only when the page reads its records from the database. The page is rewritten to:

  • explain that SetRecord() positions the page on the record's key and never hands the data to the page, so the temporary data is lost only on a database-backed page;
  • drop the "runtime error" claim and present the Learn sentence as misleading rather than as the rule's justification;
  • show Page.RunModal() with the temporary record and a SourceTableTemporary lookup page with LoadRecords() plus SetRecord() (the pattern Microsoft uses in the Dataverse option lookups) as the working alternatives;
  • list the exceptions: SourceTableTemporary = true, a TableType = Temporary source table, an OnFindRecord trigger, and the methods that are never reported.

Hugo build passes locally and the page renders at docs/analyzers/platformcop/pc0036/.

🤖 Generated with Claude Code

…orary-source exceptions

Page.SetRecord only positions a page on the record's key, so a temporary
record is only lost on a page that reads from the database. The page now
explains that semantics, shows Page.RunModal and a SourceTableTemporary
lookup page as the working patterns, and lists the exceptions.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@Arthurvdv
Arthurvdv merged commit 8adbe2e into main Nov 17, 2026
1 check passed
@Arthurvdv
Arthurvdv deleted the docs/pc0036-setrecord-positioning branch November 17, 2026 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant