code change · featureAL Developmentofficial - Microsoftreviewed - checked by Opus

#193 Clarify locale-safe DateFormula Evaluate inputs

Adds a Microsoft Style article clarifying that DateFormula Evaluate calls require language-independent literals to work correctly in non-English localizations, addressing a localization gap where such calls could fail despite correct downstream CalcDate typing.

Pull request · merged into main on 2026-09-21 by JesperSchulz · 5 files (+84 -5), 4 AL · feature · tier official · reviewed (checked by Opus)

What changed

  • New Style article: Evaluate into a DateFormula with a literal like ‘1W’ can fail outside English
  • Paired bad/good scheduling samples show the issue and the invariant-input fix
  • Style review skill gets narrow routing to the article, plus a new positive/clean evaluation pair
  • Direct CalcDate diagnostics remain owned by the analyzer (AA0462)
  • Frontmatter and index checks passed; runtime locale tests were not executed

AL objects touched

  • microsoft/knowledge/style/dateformula-evaluate-needs-language-independent-literals.bad.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/style/dateformula-evaluate-needs-language-independent-literals.good.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/style/dateformula-evaluate-needs-language-independent-literals.md: added, not in the BC? snapshot yet
  • microsoft/skills/review/al-style-review.md: modified, not in the BC? snapshot

Context

  • Systems: development, localization

Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).