MB2-716: Dynamics 365 Customization and Configuration Exam Study Notes

8/16/2020 2:07:45 PM 60 min read

Topics in Exam

Configure Microsoft Dynamics 365 (20% – 25%)

  1. Configure Microsoft Dynamics 365 settings
  2. Manage Microsoft Dynamics 365 security
  3. Configure email services
  4. Integrate Microsoft Dynamics 365 with other Office 365 offerings

Implement Microsoft Dynamics 365 entities, entity relationships, and fields (20% – 25%)

  1. Manage Microsoft Dynamics 365 entities
  2. Implement entity relationships
  3. Define and configure Microsoft Dynamics 365 fields
  4. Configure field customizations

Create and manage Microsoft Dynamics 365 solutions, forms, views, and visualizations (25% – 30%)

  1. Create and manage Microsoft Dynamics 365 solutions
  2. Customize Microsoft Dynamics 365 forms
  3. Implement Microsoft Dynamics 365 views and visualizations
  4. Configure Microsoft Dynamics 365 for mobile devices

Implement business rules, workflows, and business process flows (20% – 25%)

  1. Implement and manage business rules
  2. Implement and manage workflows, dialogs, and custom actions
  3. Implement and manage business process flows


Materials

  1. https://neilparkhurst.com/category/crm/crm-certifications/mb2-716-dynamics-365-customization-and-configuration/ Full guide of Neil Parkhurst. He covers every topic so you should read them a couple of times.
  2. https://neilparkhurst.com/2017/06/30/mb2-716-certification-microsoft-dynamics-365-customization-and-configuration-revision-guide/ It is the same courses with a master view. It is easy to navigate to the topics from this link.
  3. https://www.examtopics.com/exams/microsoft/mb2-716/ Check comments of other users because not all the answers are correct. Also read reference links of the questions.
  4. https://www.shanebart.com/mb2-716-dynamics-exam/ There is a mind mapping picture that may be helpful.
  5. https://social.technet.microsoft.com/wiki/contents/articles/37177.dynamics-365-online-limitations.aspx All Dynamics 365 Online limitations.
  6. https://andz88.wordpress.com/2017/04/03/tips-to-prepare-for-the-dynamics-365-exam-mb2-716-customization-and-configuration/ Some tips and includes useful technet articles.
  7. https://crmbusiness.wordpress.com/2016/06/21/mb2-712-crm-2016-customisation-and-configuration-hosk-study-notes/
  8. https://community.dynamics.com/crm/b/crmbusiness/posts/dynamics-365-customisation-and-configuration-mb2-716-study-notes Hosk’s study notes.
  9. https://docs.microsoft.com/en-us/previous-versions/dynamicscrm-2016/admins-customizers-dynamics-365/mt812272(v=crm.8) Integrations with other Apps.


My Study Notes:

Solutions:

  1. Includes: Schema Components, Entities, Fields, Relationships, Templates, Processes, Plugins, Forms, Views, Charts, Dashboards, Sitemaps, Ribbons, Roles,Field Security Profiles, Connection Roles,SLA, Apps.
  2. Publishers: changes entity prefixes and option sets master value. Solutions needs a publisher.
  3. Version: major.minor.build.revision
  4. Deleting an unmanaged solution only deletes the container all the components remains in the system. Deleting managed all the components and data removed from CRM.

Path Management:

  1. Created from unmanaged solution, can patch managed or unmanaged solution.
  2. Click clone as patch.
  3. Patches need to be imported in order.
  4. Clone Solution button rolls up all the patches into a higher version of solution.
  5. Patch cannot delete assets.
  6. Parent solution deletion removes all patches.
  7. After you create a patch master solution is locked until you merge the patches.
  8. https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/create-patches-simplify-solution-updates


Entity Options You cannot disable again:

  1. Business process flows.
  2. Feedback
  3. Notes
  4. Activities
  5. Connections
  6. Sending Email
  7. Queues


Forms:

  1. Entity can have multiple quick create form but only one will be active.
  2. No security roles for quick create forms, cannot switch it from form.
  3. Allow Quick Create option from entity level.
  4. Quick create form cannot include subgrid, quick view, web view, iframe, notes.


Status Reason Transitions:

You must include one inactive status reason for each status.


Views:

  1. System-Defined (special views) cannot be customized and deleted. Advanced find view, quick find view etc.
  2. Public views (system views) available to all users no security roles applied.
  3. Personal views are created from advanced find can be shared.
  4. View order is alphabetical.
  5. First 3 columns of quick find view are shown in multi-entity search. Search bar in CRM.
  6. In view you can add parent entities fields.
  7. Quick find view -> add find columns: Adds indexes to DB to speed up search.
  8. Putting 20 indices is limit for an entity and max 900 characters
  9. Special and auto created system views cannot be deleted.
  10. View removals cannot be moved by solutions you need to remove them in Production as well.


Charts:

  1. Personal charts can be exported and imported.
  2. Count All, Non-Empty, Avg, Max, Min, Sum are aggregation methods.
  3. Personal charts can be included in personal dashboards.
  4. User needs User Chart Privilege for creating personal charts.
  5. Can be included in solution.
  6. System charts are created by system admins and customizers and visible to all users. No security role applied.
  7. Tag and Doughnut can only be used in Interactive service hubs.
  8. Funnel and Pie type charts does not support multi-series data visualization.
  9. Data displayed in charts can be limited.
  10. Personal charts can be exported and imported as a system chart by admins.


Dashboards:

  1. When sharing a personal dashboard, ensure included charts and views are also shared.
  2. System dashboards does not apply security roles.
  3. Can include charts, views, iframes, web resources. And Power BI if enabled in system.
  4. Interactive dashboards are single stream and multi stream.
  5. Dashboards can be made available for tablets and phones from their properties.


Entities:

  1. System entities cannot be deleted and locked down by a solution.
  2. All activity entities are grouped under activity pointer entity.
  3. Display area Sales, Service, Marketing, Settings, Help Center.


Fields:

  1. Can be Simple, Calculated, Roll up.
  2. Calculated: Single Line of Text, Option Set, Two Options, Whole Number, Decimal, Currency, Date and Time.
  3. Rollup: Whole Number, Decimal, Currency, Date and Time.
  4. Field Formats:

Single Line of Text:

  • Email
  • Text
  • Text-area
  • URL
  • Ticker Symbol
  • Phone

Whole Number:

  • Duration
  • Time-zone
  • Language

Date and Time:

  • Date only
  • Local Time
  • Time-zone independent


Solution Entity Managed Properties:

  1. Can be customized.
  2. Display name.
  3. Can change additional properties.
  4. New forms, charts, views.
  5. Can change hierarchical relationship.
  6. Tracking be enabled.
  7. Can enable sync to external search index.


Calculated Fields:

  1. Date fields can use NOW(), ADDDAYS(), DIFF() etc.
  2. Only parent entity fields can be calculated not child entities.
  3. Saved queries, charts can only have max 10 calculated fields.
  4. Not displayed in Outlook Offline.
  5. Max complex calculation is 5.
  6. In views sorting is disabled.
  7. Cannot trigger workflows or plugins.
  8. Duplicate detection rules cannot be triggered.


Rollup Fields:

  1. Only numeric and date fields. Methods are count, avg, min, max.
  2. Waits 12 hours when first created then runs every hour.
  3. N:N relationship does not work. Cannot include complex calculated fields.
  4. Max 100 rollup for organization and 10 for an entity.
  5. Cannot rollup a rollup field.
  6. Business rules and workflows use last rolled up value.
  7. Can be triggered by workflows or plugins.
  8. Field security rules applies.


Alternate Keys:

  1. Max 5 per entity. Creates indices.
  2. Decimal, Whole, Single Text, Date, Lookup, picklist.
  3. Provide uniqueness.


Multiselect option set:

Cannot be used in business rules, business process flows and workflows.


Field Level Security:

Enabled in entity and controlled from field security profiles under security menu.


Hierarchical Relationships:

You cannot amend existing system relationships. You need to create a new one.


Entity Field Mapping:

  1. Source field must be on form.
  2. Target field applies security roles.
  3. Created from relationship of the entity.


Actions:

  1. Single entity or can be global.
  2. Can be executed from javascript, web api requests.
  3. Always run under security context of who triggers it.
  4. Actions always run in Organization Scope.
  5. Offline clients do not support actions.
  6. Can be invoked from a workflow or webservice call.


Business Process Flows:

  1. Consists of stages and steps
  2. Workflows can be triggers stepwise or global.
  3. If you hide a field, BPF is affected.
  4. Can be multiple per entity you can switch.
  5. System Processes:
  • Lead to Opportunity Sales Process
  • Opportunity Sales Process
  • Phone to Case Process
  1. Up to 10 BPFs per entity.
  2. It creates a custom entity that you can edit security roles.
  3. Set enable business processes from entity, cannot be reverted.
  4. Limits: 30 Stages, 30 Steps, 5 multiple entities, max 5 branch.
  5. Relationships is not necessary, if exists 1:N.


Business Rules:

  1. Set, Clear Fields.
  2. Sets fields requirement to required or not. But not business recommended.
  3. Show, Hide, enable, disable, lock, unlock.
  4. Show error messages in field level.
  5. Show business recommendations.
  6. Scope: Entity, All Forms, Single Form.
  7. Entity scope runs in the server like plugins. Also runs on forms as normal.
  8. Activate business rule privilege.
  9. All the fields need to be on the form.
  10. Nested if-else is not supported.
  11. Can use field, value or formula when it calculates.
  12. Only runs on form load or field change. Not On Save.
  13. Formatted whole number fields cannot be used.
  14. Max 10 if-else is supported. Mobile clients cache business rules so they need to restart the application for business rule changes.
  15. Clearing/ undoing requires a second rule.


Workflows:

  1. Only for single entity. Can be background or real time. You can convert in between unless you use a wait condition.
  2. Can be on demand and as a child process to use in other workflows or trigger manually from forms.
  3. Real time can stop record creation and plugin triggers.
  4. Real time you can chose before and after specific events. Before assign, after field update etc.
  5. You can choose execute as in real time workflows.

Security Context:

  • Background On-Demand: Runs under security context of who triggers it.
  • Background Event: Person who owns the workflow/ who created.
  • Realtime Execute as: Owner or who made the changes. If you have actions, choose owner of the workflow.
  1. Requires at least one step.
  2. Many to One when setting fields.


Integrate your email system Dynamics 365 App for Outlook:

  1. The email router is deprecated.
  2. Dynamics 365 for Outlook will be deprecated. Instead configure Dynamics 365 App for Outlook.
  3. Works in Web, Desktop Outlook App and mobile.
  4. You can track your folders via Exchange online.
  5. Drag emails to exchange inbox folder to track.
  6. Sync appointments, contacts, tasks.
  7. Security privilege is D365 App for outlook.
  8. Requires Microsoft exchange online subscription.


Folder Level Tracking:

  1. You may need to configure folder level tracking rules.
  2. You can track max 25 folders.
  3. Regarding object will be overridden every time sync occurs. You need to move email somewhere else rather than inbox in order not to track it.
  4. Queue mailboxes are not supported.


Office 365 Groups:

  1. Does not need CRM License.
  2. Requires O365 subscription or sharepoint online or exchange online.
  3. Exchange online required.
  4. For document storage, Sharepoint online needs access to OneNote Notebook.
  5. In CRM requires Server based Sharepoint integration.
  6. It is installed from Admin Center.
  7. Security privilege is ISV Extensions under miscellaneous.


OneNote Integration:

  1. Server based Sharepoint integration is required.
  2. After sharepoint integration, turn on OneNote integration.
  3. Document management and OneNote must be enabled for desired entity.


Sharepoint:

  1. There can be multiple folder locations in sharepoint but only one can be shared.
  2. There are two types of folder structure. Per entity or based on relationships.
  3. Client-side list component is not needed for server-based integrations. It is for on-premise installations.
  4. Client-side list component can give you additional capabilities like Alert me.
  5. Permissions are Sharepoint document library, Sharepoint site.
  6. Ownership of files does not change when you assign a record.
  7. Files are not deleted when you delete a record.


OneDrive Integration:

  1. 1TB to 5TB, users need O365 license.
  2. Server based Sharepoint integration is required.
  3. One drive for business privilege.
  4. Ownership of files does not change when you assign a record.
  5. Files are not deleted when you delete a record.


Mailboxes:

  1. Mailboxes are automatically created for users and queues.
  2. Each mailbox must be approved, tested, and enabled by admin.
  3. Choose server-side synchronization for email profiles as best practice.


CRM for Mobile:

  1. Enable for mobile from entities, dashboards, charts etc.
  2. Mobile read-only option in entity level does not apply for notes and activities.
  3. It uses same site map. Groupings of navigation items are ignored. They show as a flat list.
  4. Tablets: Tabs on forms become panels.
  5. Open in browser action is not available for phones.
  6. Consider adding important fields to header. It is shown first.
  7. Limits are 5 tabs, 75 fields and 10 lists. Hidden fields are included. You will need to configure visibility of fields in for phone and tablets.
  8. Views are limited to 4 fields. 3 fields and one image.
  9. You need to close and restart the application to see changes.
  10. Privilege Dynamics 365 for mobile under privacy related section.
  11. Charts are not available offline.
  12. Activity feeds and yammer is not supported for mobile.
  13. Open in browser is available for tablets.


Mobile Forms:

  1. Controls special to mobile: Number input, bullet graph, barcode scanner, radial knob, star rating, signature/pen input, Arc knob, Website preview, linear gauge, flip switch, multimedia, linear slider, auto complete.
  2. Configured from field -> add control.


Administration Settings:

  1. Once yammer is enabled you cannot disable it.
  2. Auto-numbering: Contacts, Cases, Articles, Quotes, Orders, Invoices, Campaigns, Categories, Knowledge articles.
  3. General tab you can set application name.
  4. Automatic record creation works for these entities: Email, Social activity, task, phone call, appointment, service activity and any custom activity.
  5. Automatic record creation rules can be added to solution.


Auditing:

  1. Under system settings-> Auditing-> start auditing.
  2. Reads, metadata changes, notes and attachments do not audit.
  3. After enabling auditing from system, you need to start auditing entity level and then field level.
  4. You can only delete the oldest audit log. Does not make any sense.


Data Management:

  1. You can enable duplicate detection, Sample data, create import templates etc.
  2. Enable duplicate detection you can select 3 options.
  • When record created or updated.
  • When D365 App for Outlook goes offline to online.
  • During data import.

Security:

  1. There is always on business unit on top of everything. It is first named as application name. You can change it later.
  2. There is always one team every business unit and all the users are member of this team. You cannot change that behavior.
  3. Child business units can be deleted after disabled.
  4. Business unit deletion or disabling removes all the security roles for regarding users.
  5. And users cannot login to CRM without a security role. Admin needs to give at least one role.
  6. Moving users to another business unit removes all security roles as well.
  7. Access teams does not have security roles and record ownership.
  8. You can set 2 access team templates for an entity.
  9. If someone in the access team shares a record, it conveys the privileges in access team settings.
  10. Append -> Attach this entity to other entities.
  11. Append to -> Attach other records to this entity.


Hierarchy Security:

  1. Managerial or positional.
  2. Top levels can only read non direct reports. For the direct reports they can do anything except deletion.
  3. Reads based on hierarchy depth which can be configured.
  4. Managerial works in business unit or parent business unit.
  5. Positional works beyond business units. More flexible.


Themes:

  1. Cannot change color of business process flows.
  2. Logo should be 50px deep.
  3. Cannot included in solutions. Should be exported and imported separately.
  4. The icon is not customizable.
  5. Sitemap nodes color cannot be customized.


Comments

There are no comments