Benefits and Guidelines for using a Prefix or Suffix

In your extension, the name of each new application object (table, page, codeunit), must contain a prefix or suffix. This rule applies to all objects. You can use the Caption values for what you decide to display to the user. When you modify a core Dynamics 365 object using a table extension or a page extension, the prefix/suffix must be defined at the control/field/action/group level.


Declare your objects with a prefix as shown in the following examples.


table 70000000 MyPrefixSalesperson
table 70000001 SalespersonMySuffix


page 70000000 MyPrefixSalesperson
page 70000001 SalespersonMySuffix

Page extension



codeunit 70000000 MyPrefixSalesperson
codeunit 70000001 SalespersonMySuffix


There are two good reasons to why you may want to proactively use a prefix or suffix:

  1. App A and App B both use the same field name (for a native Dynamics 365 table) of FAB Salesperson Code. The partner for App B already has the prefix/suffix reserved. A customer wants to install both apps but cannot due to collision of field name. App A will have to reserve a different unique prefix and submit an updated version of their app.

  2. Dynamics 365 developers want to use the name of Salesperson Code. App A (published for months), already has that field name. Microsoft will require the app to prefix its field names by submitting an updated version of their app.

General rules

  • The prefix/suffix must be at least 3 characters
  • The object/field name must start or end with the prefix/suffix
  • If a conflict arises, the one who registered the prefix/suffix always wins
  • For your own pages/tables/codeunits, you must set the prefix/suffix at the top object level
  • For pages/tables in the base application of BC that you extend, you must set the prefix/suffix at the top object level
  • For pages/tables of Business Central in the base application that you extend, you must also set at the control/field/action level
  • Use the AppSourceCop tool to find all missing prefixes and/or suffixes. Configuration options for this tool can be found here. The Rules section explains the different checks that the analyzer will do. For prefix/suffix detection, refer to the Configuration section. It explains how to set your prefix in the AppSourceCop.json file.

Examples of acceptable prefix/suffix

No Delimiter

  • FABSalespersonCode
  • SalespersonCodeFAB


  • "FAB Salesperson Code"
  • "Salesperson Code FAB"


  • FAB_Salesperson_Code
  • Salesperson_Code_FAB

Contact us at to reserve the prefix/suffix of your choosing

See Also

Checklist for Submitting Your App
Rules and Guidelines for AL Code