
In this video, we discuss why we created this course and the reasons you may have signed up for it. There are several reasons why this may be the case, and we explore the most likely reasons for taking this course. This is important so that you can be sure you are in alignment with the course instructor.
This lecture explains the methodology of the course, where an imaginary non-profit organization needs a software solution, and the process of requirements gathering, analysis, design, and customization to provide that solution. It also explains the nature of the imaginary non-profit organization, so you as the learner understand the nature of "our" client. In this lecture we begin the requirements gathering process, and then we provide a brief overview of Microsoft Dynamics 365. We also introduce some fundamental data relationship concepts.
In this lecture we walk through the process of branding the solution using the Themes feature in Microsoft Dynamics 365. Branding is important in the beginning because stakeholders who log into the system you are building for their early testing will feel more comfortable if the solution is branded to reflect their organization.
In this lecture we start with identifying the entities that we will need to be creating to meet the requirements for Neighborhood Assistance Programs (NAP). The entities are first identified, but before we build we must understand the relationships between the entities that we will be building. In this lecture we introduce the concept of an entity relationship diagram to carefully document how entities are related with each other. And we walk through the simple steps to create our first entity, as well as important considerations when creating an entity, such as Ownership.
Create top-level entities first, like program, then program activity, to simplify lookups across forms. Introduce a custom volunteer activity type with hours, minutes, actual start, and program, volunteer lookups.
In this lecture, we discuss and demonstrate the customizations we have completed on standard entities, such as Contacts. We also discuss certain types of customizations, such as Calculated and Rollup fields.
Learn how Microsoft Dynamics 365 goals measure actual revenue against targets with roll-up queries, goal metrics, and dashboards for nonprofits and sales teams.
Explore reporting in Microsoft Dynamics 365 by building out-of-the-box and custom reports with the report wizard, using advanced find, and exporting or Word mail-merged documents.
Explore the system settings in Microsoft Dynamics 365 to manage auditing, e-mail processing, server-side sync, display formats, calendar options, and app customization for effective administration.
When organizations search for a software solution to help them run their operation, they often must choose whether to "Build" or "Buy." It's quite difficult to find an off-the-shelf solution that meets their specific requirements, and it's expensive to hire experts to customize a solution for them.
This course is taught by a consultant that has designed, built and deployed Microsoft Dynamics 365 (and Dynamics CRM before it) for over 12 years for organizations of all sizes, from thousands of users to just one. The course invents an imaginary non-profit organization with requirements like event-planning, volunteers, and multiple program management, and walks learners through the steps of building a software solution the way professionals do it:
Requirements Gathering and Documentation
Analysis and Entity Relationship Design
Creation of entities, workflows and user interface customization
Deployment
Learners who complete this course will be able to construct a working software solution using Microsoft Dynamics 365 that is tailored to their needs. Most consulting firms specializing in Microsoft Dynamics 365 would charge between $7,500 and $15,000 in fees to build a solution the likes of which is covered in this class.
This class is not for everyone. For the class to be valuable, the prospective learner should be highly motivated to learn the principles of database entity relationships and how they are expressed in the Microsoft Dynamics 365 interface, and they should not be fearful of rolling up their sleeves and building a solution for themselves.