{"title":"AppSourceCop Warning AS0127","url":"https://jonas-paprotka.de/docs/dev-itpro/developer/analyzers/appsourcecop-as0127/","by":"JOP-AL","license":"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-as0127, 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.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0127","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Objects should be placed in a namespace with at least two levels of nesting.","date":"2026-10-01","meta":{"topic":"reference"},"outline":[{"level":1,"title":"AppSourceCop Warning AS0127","slug":"appsourcecop-warning-as0127","at":0,"chars":1995},{"level":2,"title":"Description","slug":"description","at":96,"chars":189},{"level":2,"title":"Remarks","slug":"remarks","at":285,"chars":429},{"level":2,"title":"How to fix this diagnostic?","slug":"how-to-fix-this-diagnostic","at":714,"chars":1130},{"level":2,"title":"Related information","slug":"related-information","at":1844,"chars":151}],"text":"# AppSourceCop Warning AS0127\nObjects should be placed in a namespace with at least two levels.\n## Description\nObjects should be placed in a namespace with at least two levels of nesting. This minimizes conflicts with other applications and allows the object name to not use an affix.\n## Remarks\nThe AS0127 warning indicates that objects should be placed in a namespace with at least two levels of nesting. This practice helps minimize conflicts with other applications and allows the object name to avoid using an affix. By organizing objects into namespaces with multiple levels, you can ensure better structure and avoid naming collisions, which is especially important when publishing extensions to AppSource.\n## How to fix this diagnostic?\nTo address the AS0127 warning, organize your objects into namespaces with at least two levels of nesting. This involves creating a hierarchical structure for your namespaces, which can help in managing and categorizing your objects more effectively. Here are the steps to fix this diagnostic:\nIf the object doesn't have a namespace, you should do the following:\n1. Identify the objects that aren't placed in a namespace with at least two levels of nesting.\n2. Create a hierarchical namespace structure that includes at least two levels.\n3. Move the identified objects into the appropriate namespaces within the new structure.\n4. Update any references to the moved objects to reflect their new namespaces.\nIf the object already has a namespace, you should do the following:\n1. Identify the objects that aren't placed in a namespace with at least two levels of nesting.\n1. Obsolete the objects that aren't placed in a namespace with at least two levels of nesting.\n1. In the next version of the extension, update the namespace to use at least two levels of nesting and remove the obsolete properties.\n## Related information\nAppSourceCop Analyzer<appsourcecop>\nGetting Started with AL<../devenv-get-started>\nDeveloping Extensions<../devenv-dev-overview>"}