# AppSourceCop Warning AS0098
An affix is needed.
## Description
An affix is needed.
To avoid name clashes for objects added by your extension and objects added by other extensions, an affix must be prepended or appended to the name of all new application objects, extension objects, and fields. See Benefits and Guidelines for using a Prefix or Suffix<../../compliance/apptest-prefix-suffix>.
> NOTE
> This rule mimics the behavior of appsourcecop-as0011 for a limited set of objects members for which AS0011 wasn't enforced when they were introduced in AL. Having them reported as a separate rule allows more granularity, especially in regard to AL code not respecting the use of affixes prior to the implementation of this rule.
### Which object members are validated?
The following object members are validated by AS0098:
 Enum Values defined in Enum Extension objects
 Data Items defined in Report Extension objects
 Columns defined in Report Extension objects
 Labels defined in Report Extension objects
 Keys defined in Table Extension objects on table extension fields
Other AL objects and object members are validated by appsourcecop-as0011.
## When to fix this diagnostic?
### For new object members
For objects that are introduced with the current version of the extension, appending one of the mandatory affixes to the object's name will fix the diagnostic.
Renaming objects which are not part of the baseline is allowed.
### For existing objects
For objects which already exist in the version of the extension used as baseline, it is not possible to rename them. It is therefore not possible to append one of the mandatory affixes. Instead, the offending object should be deprecated using the ../properties/devenv-obsoletestate-property property and a new object whose name has one of the mandatory affixes should be introduced.
For detailed examples, see appsourcecop-as0011.
> IMPORTANT
> Introducing a new enum value can be a breaking change if this enum value is stored in the database. You must carefully assess the impact of your changes before introducing a new enum value. This implies writing upgrade code for your app and for the dependent extensions storing this enum value in their own tables.
## Related information
AppSourceCop Analyzer<appsourcecop>
Get Started with AL<../devenv-get-started>
Developing Extensions<../devenv-dev-overview>

Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0098, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact. https://jonas-paprotka.de/docs/dev-itpro/developer/analyzers/appsourcecop-as0098/
