Naming convention for new fields

(0) Share

Report

Posted on by Samantha73

3,247

Hi All

If we are adding new fields to existing entities do we have to follow any conventions? For example, if I add Address2 as a field to the account and later Microsoft adds the same field name will there be a conflict? Is it better the name fields with a prefix like ABC_Address2?

Thanks

I have the same question (0)

All responses (2)

Answers (2)

Verified answer

Community Member on at

Like (0)

Report

Hi Samantha73,

Don't worry about it, the conflict does not normally occur.

Every solution has a publisher. The default solution has a publisher named “Default Publisher for <your organization name>”.

The publisher record contains a Prefix value. The default value of this prefix is “new”.

Go to Settings > Customizations >Publishers.

'

So when i create a new custom field, the 'new' prefix will be filled automatically.

And you can change the prefix with any value you want:

Test:

Was this reply helpful? Yes No
Verified answer

Bipin D365 28,983 Moderator on at

Like (0)

Report

Hi,

One thing which I would recommend is to always create your own publisher record with your own prefix and then create new solution, use publisher you just created for new solution.

Now always create new fields from your solution, Do not create fields/entities from default solution.

The naming covention which I follow and best practices are -

Lookup field - add 'id' in the end of the schema name for example - prefix_contactid

optionset - add 'code' in the end of the schema name for example - prefix_contacttypecode

Please mark my answer verified if this is helpful!

Regards,

Bipin Kumar

Follow my Blog: xrmdynamicscrm.wordpress.com/

Was this reply helpful? Yes No