In xRM development, nearly every solution requires some custom development in order to extend Dynamics CRM for business scenarios outside CRM functions such as sales force automation and customer service. As with any software development, strong naming standards will help your developers and testers save time and produce a better solution.
Here are some modest suggestions:
Here are some modest suggestions:
- Be generous in comments inside your code. The next developer who takes over will thank you.
- Provide unified coding standards on the JavaScript libraries.
- Use consistent file naming conventions.
- Use only one .JS file per form for the form-specific logic.
- Don't write JavaScript event handlers from the control property window rather than as part of the JavaScript file associated with the form.
- Create standard common function libraries, to address common functionality across forms.
- Use JavaScript or business rules (in Dynamics CRM 2013) to show/hide/enable/disable controls rather than creating multiple similar forms.
- Be consistent in designing the user interface, using the same control types with an eye toward the user experience.