Tomas Kapitan
Tomas Kapitan
It's related to this AL issue: https://github.com/microsoft/AL/issues/7057
Hi @anzwdev, I've finally some time to try add the codecleanup actions to our projects. This "Sort Triggers" option is interesting, but I have the same problem as @fvet. We...
@Arthurvdv I get this warning with the latest release, caused by the pragmas below. 
@Arthurvdv @StefanMaron Yes, I believe excluding the objects that are not part of the App is correct solution. We have now 150+ warnings in most of the apps for base...
@StefanMaron what should this message for objects not under our control indicate? What should be the steps to fix the code without pragma? I like the rule for my own...
@StefanMaron What’s the difference in this case of having it in CU or in a tableextension?
@StefanMaron still not sure that this is working completely (sorry for using this issue; it's probably not specifically related to table extensions. This warning can be fixed by - Adding...
I was forced by our dev team to disable the rule as they don't agree with moving all code from reportextensions to codeunits. I'll try to test a bit more...
@krupybalu @BazookaMusic Can you please have a look? This shouldn't be hard to fix and it currently prevents partners to use these new functions.
The same problem happens in tableextension in combination with local procedures/global variables on the tableextension level.