Prefix code for developing Business Apps on Microsoft AppSource

posted by Category: Dynamics 365, Dynamics NAV, Microsoft Dynamics, Troubleshoot 0 Comment
developing business apps on microsoft appsource

If you want to develop business applications (extensions) for Microsoft Dynamics 365 Business Central on AppSource, you have to request and register 3-Character prefix/suffix code for your organization with Microsoft. Dynamics 365 Business Central team will then reserve this code for you and you have to use this code for apps development.

For example, we had registered “INT” as our company’s unique code.

Here are some points to keep in mind about this unique prefix/suffix code.

  • Object prefix must be registered with Microsoft (at least 3 digits) and must be unique (it’s globally reserved for you)
  • It can be a prefix or a suffix i.e., you can call an object XXXMyTable or MyTableXXX
  • You have to use it for every objects in your extension
  • This is not case sensitive i.e., you can call an object XXXMyTable or xxxMyTable
  • You can use the prefix in any format you want. So, XXX_MyTable, XXX-MyTable, XXX.MyTable, XXX MyTable etc. are all valid names.
  • You can register more than one prefixes. So, you can have a prefix per app but a specific prefix for a company is preferred.
  • Functions in your extension objects cannot have the prefix/suffix in names. The prefix is in your object name, so you can have something like XXX-MyCodeunit.MyWonderfulFunctionNameLongAsIWant() )
  • If you have an extension A that depends on the extensions B and C, both B and C adds a function MyFunction to a standard table (Customer table for example), if you call Customer.MyFunction you receive an error on compilation (ambiguous call)
  • If you create any extended page/table object than object name should contain it. E.g.  pageextension 70144371 INT ExtendItemCard extends “Item Card”
  • Use in name of field added in standard table (by extended tales object)
  • Use in name of action/group added in standard page/role center, see the following example:

actions

    { 

       addafter(“Purchase Invoice”) 
        { 
            group(“INT Item Generator”) 
            { 
                action(“INT Item Configurator List”) 
                { 
                    Caption = ‘Item Configuration’; 
                    ApplicationArea = all; 
                    Image = ItemTracking; 
                    Promoted = true; 
                    PromotedCategory = Process; 
                    PromotedIsBig = true; 
                    RunObject = Page “INT Item Configurator List”; 
                } 

All in all, Microsoft requires you to have your extension object name unique so that the conflict between n number of extensions in AppSource can be removed.

You can check out the Business Apps  developed by us for Dynamics CRM and Dynamics 365 Business Central.  Contact us if you need help in developing business apps on Microsoft AppSource.

About Nilesh Gajjar

My name is Nilesh Gajjar. Working as Microsoft Dynamics NAV Technical Consultant Technical Team Lead at Intech-Systems Pvt. Ltd. in Ahmedabad since 2012.This is my blog where I post things related to Microsoft Dynamics NAV, I am hoping you find useful and interesting things here.
Technical Team Lead

My name is Nilesh Gajjar. Working as Microsoft Dynamics NAV Technical Consultant Technical Team Lead at Intech-Systems Pvt. Ltd. in Ahmedabad since 2012.This is my blog where I post things related to Microsoft Dynamics NAV, I am hoping you find useful and interesting things here.

Write a comment