#2286 fix: Refactor GetModifiedSettingsContent for PS5 compatibility
The GetModifiedSettingsContent function now explicitly lists property names instead of using wildcards in Select-Object to ensure compatibility with PowerShell 5.
- 3files
- 1AL files
- 0objects
Pull request · merged into main on 2026-07-14 by ChrisBlankDe · 3 files (+20 -1), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Fixed property handling in GetModifiedSettingsContent function
- Explicitly lists properties instead of wildcard expansion
- Prevents literal ‘*’ property from being added in PowerShell 5
- Improves PowerShell 5 compatibility
- Includes unit tests for the change
- Behaviour changes for users or extensions.
AL objects touched
Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1: modified, not in the BC? snapshot
Context
- Systems: platform
Source: metadata of a merged pull request in microsoft/AL-Go (al-go): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).