LinterCop rule LC0068 warns when a Business Central AL object is missing the Permissions property for table data it accesses — a critical check for indirect permissions. Without it, users who rely on indirect access will hit runtime errors that are difficult to trace back to the missing declaration.
This stream works through three confirmed false positives in the LC0068 implementation: the Integer virtual table triggering unnecessary warnings, XMLPort table elements with AutoReplace/AutoSave/AutoUpdate all set to false requiring unneeded modify permissions, and a case-sensitivity bug in the InherentPermissions attribute check. Each fix is implemented and tested against LinterCop's Roslyn-based test suite.
As a bonus, the stream also covers the MSDyn365BC.Sandbox.Code.History repository — a GitHub Actions-powered nightly diff of Business Central sandbox builds across 50 country versions, and how to clone it selectively without pulling down the entire 250-branch history.
Streaming all kinds of coding for Microsoft Dynamics 365 Business Central.
Join me to just hang out or tell me what I am doing wrong ;)
Join me live and let's build this together.
📝 Blog post: https://stefanmaron.com/posts/linterc...
https://github.com/StefanMaron/Busine...
https://github.com/StefanMaron/MSDyn3...
====== Content of this Video ======
0:00 - Introduction and stream setup
1:09 - Announcement of Microsoft MVP selection
2:59 - Discussing AL Rule for indirect permissions
5:55 - Fixing issues with the AL Rule
17:47 - Addressing XML Port warnings
25:52 - Handling inherent permissions
34:50 - Investigating Rec.FindFirst() issue
1:20:52 - Introduction to MSDyn365BC.Sandbox.Code.History
1:24:24 - Explaining GitHub Actions workflow
1:27:18 - Demonstrating partial clone of repository
1:32:35 - Comparing versions in the repository
1:36:14 - Closing remarks and future streams
About Me:
https://stefanmaron.com/
Music by:
/ @streambeatsbyharrisheller
https://open.spotify.com/artist/6GTRL...