Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Define your extensibility strategy
Done? | Task |
---|---|
✓ | Make sure that you only extend the solution when it empowers users or adds value to the business. |
✓ | Don't try to copy the same results as the legacy solution or the system you're replacing. |
✓ | Understand the platform capabilities and use them to simplify and optimize the process. Use the out-of-the-box features as much as possible. |
✓ | Check if there are any independent software development (ISV) organizations that can meet your needs before you decide to extend the solution. The AppSource marketplace has ISV-managed solutions that might replace the need for a custom solution. |
Considerations
Done? | Task |
---|---|
✓ | Test how the extensions affect the user experience, responsiveness, performance, and cross-device behavior. |
✓ | Make sure that the extensions follow the security, privacy, and compliance requirements. |
✓ | Make sure that the extensions can handle high volume and peak seasons. |
✓ | Use ALM automated processes to build and deploy the extensions efficiently and quickly. |
✓ | Use only the documented supported techniques for code and customizations. Don't use deprecated features and techniques. |
Next steps
- See how other organizations extended their Dynamics 365 apps to meet their business needs in scenarios for extending Dynamics 365.
- Learn more about the specific considerations and best practices for extending finance and operations apps and for extending customer engagement apps.
- Read the case study of how a company extended its Dynamics 365 app to improve its customer service.
- Use the Success by Design checklist to plan and implement your extensions effectively.