Customization Best Practices
Just came across this list of custmization best practices to follow in the CRM SDK 4.0.10. Using Custom Entities and Attributes ISV solutions can save data by using: • Custom attributes on existing entities • Custom entities • A separate database • Use entity rename to make system entities more meaningful You should use a unique prefix for custom entities and attributes. For example, use an abbreviation of your company name to avoid conflicts with other ISV add-ins. Using Isv.Config.xml Microsoft Dynamics CRM ships with a sample configuration file in the wwwroot_Resources folder. To prepare for installation of ISV add-ins you should rename this file and then create your own configuration file. By doing this you will not confuse the sample UI changes with the UI changes you need for your customization. ISVs should merge changes into the existing ISV.Config file and not overlay the existing configuration file. When Do I Add vs. When Do I Customize an Entity? You should customize a system...