How To: Microsoft Dynamics 365 Best Practices for Custom Forms
When creating a custom model-driven app for Dynamics 365, it is recommended to clone one of the out-of-box Microsoft forms on the primary tables used in the app. This ensures that any changes made to the default form by Microsoft won't affect the production environment. It is also suggested to limit the model-driven app to just one main form to minimize the chance of inexperienced users accessing the wrong form. Additionally, when copying an existing form, it is important to check and adjust the security settings to allow access to the custom form. Forgetting to do this may result in the custom app displaying all forms enabled for "Fallback" instead of the desired form.
Article 3w
Login now to access my digest by 365.Training
Learn how my digest works
Features
- Articles, blogs, podcasts, training, and videos
- Quick read TL;DRs for each item
- Advanced filtering to prioritize what you care about
- Quick views to isolate what you are looking for right now
- Save your favorite items
- Share your favorites
- Snooze items you want to revisit when you have more time