#AppSourceCop
LightNews LightNews
sosicstefan.bsky.social
Microsoft has rolled out several updates to AppSourceCop, the AL code analyzer used to validate extensions for AppSource... ⬇

ssosic.com/development/...

#msdyn365bc #AppSourceCop
AppSourceCop Updates: What Developers Need to Know - Stefan's BC Blog
Microsoft has rolled out several updates to AppSourceCop, the AL code analyzer used to validate extensions for AppSource. These changes aim to strike a better balance...
ssosic.com
July 29, 2025 at 4:40 PM
nataliekarolak.bsky.social
These AppSourceCop rule updates were published with AL language v15.2.1630495:
Updated rule AS0018 to allow removing or renaming events in extension objects when the event name conflicts with the name of the events defined in the target object. Updated rules AS0034 and AS0039 to allow modifying the InherentEntitlments on tables. Updated rule AS0106 to allow removing protected global variables conflicting with built-in members. For instance, variables named Language on reports which conflict with the built-in Language method. Updated rule AS0034 to be more strict about the Compressed property, because changing it could lead to extensions not being able to update. Now it will be an error to change the property from true to false and vice versa. The default value is true, so adding the property with false will similarly be considered a breaking change. Adding new AppSourceCop configuration settings enabling validation of breaking changes on objects which are Obsolete, marked with OnPrem, or marked with Internal accessibility. By default, these objects are not validated by AppSourceCop nor by the AppSource technical validation process. For more info, see AppSourceCop Configuration. New rule AS0134 to detect breaking changes of the version attribute parameter of external business events. The rule will not fail AppSource submissions as the default severity is Warning. New rule AS0135 to validate that external business events are correctly obsoleted prior to removal.
July 14, 2025 at 7:24 AM
nataliekarolak.bsky.social
🆕 𝗔𝗽𝗽𝗦𝗼𝘂𝗿𝗰𝗲𝗖𝗼𝗽 𝗘𝗿𝗿𝗼𝗿 𝗔𝗦𝟬𝟭𝟯𝟱
learn.microsoft.com/en-us/dynami...

One-step removal of the external business event is not allowed as it can introduce breaking changes for external subscribers.
July 3, 2025 at 9:24 AM
nataliekarolak.bsky.social
🆕 𝗔𝗽𝗽𝗦𝗼𝘂𝗿𝗰𝗲𝗖𝗼𝗽 𝗪𝗮𝗿𝗻𝗶𝗻𝗴 𝗔𝗦𝟬𝟭𝟯𝟰
learn.microsoft.com/en-us/dynami...

The version attribute parameter of an external business event cannot be changed because it might break external subscribers.
July 3, 2025 at 9:24 AM
nataliekarolak.bsky.social
A few upcoming AppSourceCop rules are already documented: 🧵

- Warning AS0134 - The version attribute parameter of an external business event cannot be changed.

- Error AS0135 - External business events must be marked obsolete before they can be removed.
July 3, 2025 at 9:24 AM
nataliekarolak.bsky.social
The pre-release version of the AL Language (16.x) adds new AppSourceCop config settings to enable validation of breaking changes on symbols which normally aren't checked: internal, obsoleted, OnPrem.

𝗔𝗽𝗽𝗦𝗼𝘂𝗿𝗰𝗲𝗖𝗼𝗽 𝗔𝗻𝗮𝗹𝘆𝘇𝗲𝗿 𝗥𝘂𝗹𝗲𝘀 - 𝗖𝗼𝗻𝗳𝗶𝗴𝘂𝗿𝗮𝘁𝗶𝗼𝗻
learn.microsoft.com/en-us/dynami...
validateInternalSymbols: Specifies whether the breaking change validation should be enabled on internal symbols. By default, the validation of breaking changes is performed only on symbols that are part of the public API (except for schema breaking change validation which is always performed). validateObsoleteSymbols: Specifies whether the breaking change validation should be enabled on symbols which are obsolete in the baseline. By default, the validation of breaking changes allows breaking change done on symbols which are obsolete in the baseline (except for schema breaking change validation which is always performed). validateOnPremSymbols: Specifies whether the breaking change validation should be enabled on OnPrem symbols. By default, the validation of breaking changes is generally performed only on symbols with scope Cloud (except for schema breaking change validation which is always performed).
June 17, 2025 at 2:34 PM
nataliekarolak.bsky.social
The AppSourceCop.json has been enhanced with the 𝘀𝗼𝘂𝗿𝗰𝗲𝗠𝗼𝘃𝗲𝗱𝗢𝗯𝗷𝗲𝗰𝘁𝘀𝗣𝗮𝗰𝗸𝗮𝗴𝗲𝘀𝗖𝗮𝗰𝗵𝗲𝗣𝗮𝘁𝗵 setting. It is now also documented in article 𝗔𝗽𝗽𝗦𝗼𝘂𝗿𝗰𝗲𝗖𝗼𝗽 𝗔𝗻𝗮𝗹𝘆𝘇𝗲𝗿 𝗥𝘂𝗹𝗲𝘀 -
Configuration
learn.microsoft.com/en-us/dynami...
The path to the folder containing the packages from which tables or fields are moved to the current application. It should also contain their dependencies. If empty, move validation is disabled.
April 2, 2025 at 7:48 AM
nataliekarolak.bsky.social
𝗔𝗽𝗽𝗦𝗼𝘂𝗿𝗰𝗲𝗖𝗼𝗽 𝗘𝗿𝗿𝗼𝗿 𝗔𝗦𝟬𝟭𝟭𝟲
learn.microsoft.com/en-us/dynami...

🆕 Setting up AppSourceCop to validate moved symbols
learn.microsoft.com/en-us/dynami...
In order to set up AppSourceCop to validate moved symbols, the property sourceMovedObjectsPackagesCachePath must be set in the AppSourceCop.json file to point to a directory which will contain baseline packages for all the applications from which symbols are moved. If this is not set, validation is disabled. AppSourceCop will try to find the source applications from the dependencies of the current application first and then from all the packages which are placed in that directory. Thus, if a symbol is being moved from a dependency of the application, setting the property and leaving the directory empty will be enough. Otherwise, the source application needs to be compiled and copied or moved into the directory.
April 2, 2025 at 7:36 AM
nataliekarolak.bsky.social
𝗔𝗽𝗽𝗦𝗼𝘂𝗿𝗰𝗲𝗖𝗼𝗽 𝗘𝗿𝗿𝗼𝗿 𝗔𝗦𝟬𝟬𝟬𝟭 (Tables and table extensions that have been published must not be deleted.)
learn.microsoft.com/en-us/dynami...

🆕 Added explanations (see image) and examples (learn.microsoft.com/en-us/dynami...).
Only if the target table of an extension has been deleted, then the table extension can be deleted as well. There's an exception for table extensions that target Microsoft tables, which have either been deleted or marked with `ObsoleteState = Removed`. In this case, it's possible to remove the table extensions as long as the extension requires a runtime with version '13.0' and higher.
March 26, 2025 at 7:49 AM
nataliekarolak.bsky.social
Assisted by AI, Microsoft has just 𝗲𝗻𝗵𝗮𝗻𝗰𝗲𝗱 𝟭𝟯 𝗔𝗽𝗽𝗦𝗼𝘂𝗿𝗰𝗲𝗖𝗼𝗽 𝗿𝘂𝗹𝗲 𝗮𝗿𝘁𝗶𝗰𝗹𝗲𝘀. #msdyn365bc

For example, AS0125: learn.microsoft.com/en-us/dynami...

To review 𝗮𝗹𝗹 changes:
github.com/MicrosoftDoc...

Are you happy with this approach? Let Microsoft know at www.yammer.com/dynamicsnavd...
January 15, 2025 at 3:40 PM
nataliekarolak.bsky.social
The AppSourceCop has a rule (an error) to prevent that: AS0062
learn.microsoft.com/de-de/dynami...

Even if you are not an AppSource developer, you could theoretically activate the AppSourceCop as well, just disable all other rules than AS0062.
December 16, 2024 at 9:05 AM
nataliekarolak.bsky.social
Big news, developers for #msdyn365bc AppSource !

🆕 As soon as you use namespaces, you can omit the affix for new objects (top level only) - AppSourceCop will permit

Mind that affixes still need to be registered for the app, even if you don't use them.

Here's what you will find in the docs:
December 12, 2024 at 3:47 PM