Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance forum / Model name best practices
Finance forum
Unanswered

Model name best practices

(0) ShareShare
ReportReport
Posted on by CU04051814-0
Hi,

Is it a best practice to name the model as PrefixExtension like this?


Because I know that when we create an extension for an object like SalesTable Form, then it should be like SalesTable.ZZZExtension. So in this case, this name will be filled automatically.
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,642 Super User 2024 Season 2 on at
    Model name best practices
    Hi,
     
    Both options look OK to me. Can you share the exact BP warning you get for the label file? I'm aware that the contents can give a BP warning about label numbers versus descriptive IDs.
  • Martin Dráb Profile Picture
    Martin Dráb 230,371 Most Valuable Professional on at
    Model name best practices
    It's up to you (documentation: Include either the name of the model where the extension element resides or the prefix that the extension is associated with).
  • Martin Dráb Profile Picture
    Martin Dráb 230,371 Most Valuable Professional on at
    Model name best practices
    The documentation does not say that you must use the Extension suffix. Let me quote it: "an extension of the ContactPerson table in the ContosoCustomizations model might be named ContactPerson.ContosoCustomizations".
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,642 Super User 2024 Season 2 on at
    Model name best practices
    Hi,
     
    As mentioned below, I agree that the model naming should not have an abbreviation as a prefix or suffix. Just name it to describe what the contents are about. In case you might expect similar model names to be used by different parties, then you can include e.g. a vendor name. If the model is e.g. about Commodity trading, then you can describe it as Contoso Commodity trading.
     
    The link to the naming conventions you shared is about the object names in the model. Yes, that is best practice to follow as much as possible.
  • Suggested answer
    Komi Siabi Profile Picture
    Komi Siabi 12,729 Most Valuable Professional on at
    Model name best practices
    Hello, 
     
    You can just name the model after the company name. That's more than enough. 
     
    GEMS as model name. CustTable extension will be CustTable.GEMS.
  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 230,371 Most Valuable Professional on at
    Model name best practices
    I wouldn't do that and because no standard model (AFAIK) does that either, we can safely say that it's not a best practice.
     
    I wouldn't add an Extension suffix to all extensions. In my opinion, it's already clear that it's an extension. Instead of wasting characters with Extension and using just three characters (ZZZ) for identification of the product (or company), utilize the character for a longer name.
     
    For example, if it's a model for customizations for company MyCompany, you can call both the model and extensions MyCompany, instead of something like MYCExtension.

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

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

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

#2
Martin Dráb Profile Picture

Martin Dráb 230,371 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans