publisher custom entity prefix

(0) Share

Report

Posted on by Community Member

Hello, for an otb crm installation, the default publisher has a custom entity prefix of "new". The following url recommends changing the custom entity prefix for the default publisher to something that identifies the related company for the publisher:

http://msdynamicscrmblog.wordpress.com/2013/11/15/solutions-in-dynamics-crm-2013/

I've noticed that the publishers installed for third party managed solutions in my environment follow this pattern. This makes sense to me because custom entities that were created for third party solutions should be identifiable from custom entities that were created for the primary solution.

However, I was wondering how common it is for crm implementors to change the custom entity prefix to identify the company for the primary in-house crm implementation. Do you find that most implementors keep the default prefix of "new"? What would you recommend for a brand new crm installation in this scenario?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (2)

Verified answer

Joe Gill on at

Like (0)

Report
Copy link

Link copied!

Hi Andrew,

In my experience most customizers do change the prefix to their company's initials

hth

Joe

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks Joe. The handful of on-site implementations I've been on have used the default prefix of "new" but the implementors were probably not aware that the prefix could/should be changed. I'd be interested to get feedback from others as well.

A company could have several different CRM implementations so using company name as the default prefix would not differentiate between CRM implementations at the same company. Using a prefix of CompanyName.DivisionName would be more unique but this approach would require extra time for typing that could add up and potentially slow down development. These are just a few thoughts on potential downsides of this approach but I'd be interested in counterpoints to this.

Was this reply helpful? Yes No
Verified answer

Joe Gill on at

Like (0)

Report
Copy link

Link copied!

I think using a short prefix is good practice so rather than using CompanyName.DivisionName you would have

use something like xyzsales

l

I have seen deployments with different prefixs for different solutions in the same organization to help identify what the customization relates to e.g. xyzsales and xyzsupp

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

@Joe - thanks for the insight. Do you know of any official microsoft/msdn url that describes this as a recommended pattern along with the reasoning behind it? Having that reference would make it easier for me to convince a team to adopt the pattern as a standard.

Was this reply helpful? Yes No
Amol Deshmukh 40 on at

Like (1)

Report
Copy link

Link copied!

Hi,

i need help on following point

1. i want publisher name of custom entity in code (while creating plugIn)

2. then i want prefix of that publisher

Was this reply helpful? Yes No