Skip to main content

Notifications

Announcements

Join us in the Community for an AMA: December 12th Register Today
News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Best practise for naming
Finance | Project Operations, Human Resources, ...
Suggested answer

Best practise for naming

(0) ShareShare
ReportReport
Posted on by Dev 390
Hi ,
 
There is a little confusion regarding the naming convention for the objects.
In general we name the objects as OrganisationNamePrefixObjectName (ABCUpdateSalesInvoice ABC being organisation name for e.g) for new objects and OrganisationNameObjectName.Extension for extension object which can also be .ModelExtension in some cases.
But for some customers they do not want to have organisation name as they might change in later stages so please suggested the best naming strategy in this case.
 
Thanks!
  • Martin Dráb Profile Picture
    Martin Dráb 229,963 Most Valuable Professional on at
    Best practise for naming
    Kevin, thanks for another reply completely missing the point. These off-topic or utterly wrong generated answers decreases usefulness of this forum. If you keep generating content regardless of whether it's useful, I think that admins will have to take some action sooner or later. Please think about it.
  • Suggested answer
    Kevin Xia Profile Picture
    Kevin Xia Microsoft Employee on at
    Best practise for naming
    Hi,
    When customers prefer not to include the organization name due to potential changes in the future, it's wise to adopt a more flexible strategy. Consider the following naming approach:
    New Objects:
    Use a generic prefix or abbreviation that represents the application or module.
    Follow it with the object name.
    Example: INVUpdateSalesInvoice
    Extension Objects:
    If an extension includes the model, use a clear and concise extension identifier.
    Avoid tying the extension directly to the organization name.
    Example: SalesInvoiceExtension or SalesInvoice.ModelExtension
    Best regards,
    Kevin
  • Layan Jwei Profile Picture
    Layan Jwei 7,322 Super User 2024 Season 2 on at
    Best practise for naming
    Hi Dev,

    As Martin said, it doesn't have to be the organization name. Maybe stick to modelName Prefix. Or choose any prefix as long as it's unique.  -- as the idea of the prefix is to avoid conflicts with other elements.


    Here's what Microsoft documenation says about naming conventions:
    https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/naming-guidelines-extensions

    Thanks,
    Layan Jweihan
  • Martin Dráb Profile Picture
    Martin Dráb 229,963 Most Valuable Professional on at
    Best practise for naming
    It doesn't have to be the current organization name or an organization name at all, but it needs to be something (hopefully) unique, to avoid naming conflicts with objects created by Microsoft, ISVs etc. Maybe you can give a name to the the implementation project that has a chance to survive renaming of the company (if it's so common with your customers) and derive the prefix from the project name instead of the company name.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join us in the Community for an AMA: December 12th Register Today

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

New! Quick response templatesâš¡

Save time with the new custom templates!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,151 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 229,963 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans