Dynamics makes it easy to extend its out of box standard field set to meet your company's needs. You can add your own custom fields to the out of box entities as you need, but you'll want to be sure to follow these best practices!
The system will not allow you to create two fields with the same field name however, you can create two fields with the same display name.
If you're familiar with using multiple forms in Dynamics, then you know that you can create different forms and assign security roles so that different users see a different form for a specific entity. This can get rather complicated depending on how many forms you are using and if you are using a layered security approach where a user may have multiple security roles that are applied to different forms.
What is Dynamics Tidbit Tuesday @ 2?
Beringer Technology Group is proud to announce our new monthly webinar series - Dynamics Tidbit Tuesday @ 2. We will be hosting a 30 minute webinar the 2nd Tuesday of every month at 2:00 PM ET. These sessions will be a way for us to share our vast experience and expertise of Microsoft Dynamics 365 with you.
What is a Business Rule?
Simply put, a Business Rule is a code-free way to apply rules to a form in Dynamics. You can use a Business Rule to set field values, clear field values, set field requirement levels, show or hide fields, enable or disable fields, validate data and show error messages, or create business recommendations based on business intelligence.
Best Practices for System Views and My Views in Microsoft Dynamics 365
This is my 7th blog in my 12 part series on Microsoft Dynamics Best Practices. If you've missed any of my previous blogs, please check them out by clicking here! If you're interested in learning more about Dynamics Best Practices, they are a great place to start.
I'm halfway through my Best Practice series and I am loving the feedback that I've received so far. For this blog, I'm going to touch on three very important best practices that you should follow. Not just with Dynamics, but with any system that you work with whether it be implementing or just administering and maintaining.
This is the fourth blog in my 12 part series focusing on Microsoft Dynamics 365 Best Practices. If you've missed my previous blogs, they've focused on defining Best Practices, Organizations, and Solutions and Patches. For my remaining blogs, I'm going to focus on the different components in Dynamics 365, starting with Entities.
This is my 3rd blog in my 12 part series that talks about Microsoft Dynamics 365 Best Practices. My first blog focused on defining the term "Best Practice" in relation to Dynamics 365. This blog focuses on Dynamics 365 Solutions and Patches Best Practices.
This is my 2nd blog in my 12 part series that talks about Dynamics 365 Best Practices. My first blog focused on defining the term "Best Practice" in relation to Dynamics 365. This blog focuses on Dynamics 365 Organizations Best Practices. All future blogs, will focus on Best Practices surrounding different configuration topics relating to Dynamics 365.
Congratulations on your choice to use Microsoft Dynamics 365. You have purchased a Production instance.
Dynamics 365 Best Practices
One of the great features of Dynamics 365 is that you can easily configure the system to meet your needs. Creating new entities, fields, and views can be done through the current interface and without the need to have development knowledge and write code.