publisher custom entity prefix RRS feed

  • Question

  • 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:


    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?

    Friday, May 23, 2014 9:52 PM

All replies

  • Many partners or ISVs will prefix their customizations with something that represents their company - that way its easy to identify to source of a particular field. Then update the default publisher to be something that represents the actual user's organization. Typically users will make updates to the default solution and end up with fields and entities prefixed with whatever the default publisher is set to. Really nobody should be using "new" as the prefix for anything in my opinion. 

    Jason Lattimer
    My Blog -  Follow me on Twitter -  LinkedIn

    Saturday, May 24, 2014 2:43 AM