# Marketplace names, affixes, and ID ranges FAQ
This article addresses some of the most frequently asked questions around how affixes and ID ranges are assigned to Marketplace apps.
## Do I need to register different affixes for each of my extensions?
No, you don't need to register affixes for each of your extensions.
The object affixes are registered per publisher so if your apps all have the same publisher, they can share the same affixes. The automated validation verifies that you're using the three letters affix registered by Microsoft in your extension, but this still allows you to create longer affixes per extension. For example, if you registered ABC as your affix, you can use ABCD as the prefix in Extension 1 and ABCE as the prefix in Extension 2. See Prefix and suffix for naming in extensions<../compliance/apptest-prefix-suffix>.
## Do I need to request a different ID range for each of my extensions?
No, you don't need to request a new ID range for each of your extensions.
The object IDs are registered per partner, not per extension. You can then use a subset of this range for each of your extensions. It is your responsibility to ensure that you aren't defining objects with the same IDs in different extensions. If you're doing so, the extensions defining these objects can't be installed together on the same environment. See Get started building apps<readiness/get-started#requesting-an-object-range>.
## Will there be any changes made to the object names character limitation (30 characters) within the near future?
We would like longer names as well. Introducing namespaces could be one investment. However, such a change has down-stream breaking impact (any caller needs to qualify calls) and there are SQL constraints on name lengths for tables, which currently include company name, table name, app ID and needs to be maximum 255. This is on our long term backlog, but haven't any changes planned soon.
## Related information
Technical validation checklist<devenv-checklist-submission>
Technical validation process FAQ<devenv-checklist-submission-validation-process>
App identity FAQ<devenv-checklist-submission-app-identity>
Azure Application Insights and Marketplace submission FAQ<devenv-checklist-submission-app-insights>
Marketplace app previews FAQ<devenv-checklist-submission-app-preview>
Business Central offer FAQ<devenv-checklist-submission-offer>
Names, affixes, and ID ranges FAQ<devenv-checklist-submission-name-affix-range>
Develop and maintain Marketplace apps FAQ<devenv-checklist-submission-develop-maintain>
Code-signing validation FAQ<devenv-checklist-submission-code-sign>
Channels for questions and issues FAQ<devenv-checklist-submission-channels>

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/devenv-checklist-submission-name-affix-range, 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/devenv-checklist-submission-name-affix-range/
