MB2-715 Certification: (Microsoft Dynamics 365 Customer Engagement Online Deployment) – Revision Guide

Thanks for great stuff altogether!!

Microsoft Dynamics 365 and Unified Service Desk

I have been completing a series of posts to help people prepare for the MB2-715 certification (Microsoft Dynamics 365 Customer Engagement Online Deployment). Here is a collection of links to all of those posts. I hope these might serve as a useful revision aid for the MB2-715 exam.

The MB2-715 certification is not easy! But deployment is an important topic and one you will really enjoy learning about.

In my opinion the MB2-715 differs slightly in its style to some of the other certifications such as MB2-716 (customization). As its scope contains some topics that are possibly more theoretical, such as how plan for updates or understanding the licensing options. But even so, I still encourage everyone to try as many of the features discussed hands on. Do not rely on theory alone!

Introduction

Create a Customer Organizational Structure

Support the Microsoft Dynamics 365 client environment

  • Validate minimum browser requirements…

View original post 501 more words

Advertisements

Field Service: Sample data installation

While studying Field Service, Field Service installation is not enough,  we need to install sample data or seed data in the environment, so we will get clear idea of how its looks like and we can play with that sample data just like real one. As well, it can be used for demo purpose. So … Continue reading Field Service: Sample data installation

Open create ‘Form’ from sub-grid directly by avoiding associated records between entities

In MSD 365, when we add sub-grid on form by creating relation between two entities, it will gives Create (+) button and associate view button. When we click on Create (+) button, dynamics shows already created associations between these two entities, ref below screen shots... Some time we don't require this associated records and always … Continue reading Open create ‘Form’ from sub-grid directly by avoiding associated records between entities

Creating empty XRM Environment in PowerApps

Good one !!

There was a one of seminar on the same topic in CRM Saturday-Sydney by Guy Riddle.  It was awesome. As well, I was looking for that process, and this is the one.   Thanks !!

Courtesy: https://bettercrm.blog

If you are following the latest news regarding Dynamics 365 ecosystem, you are probably aware of the fact that Microsoft decided to put everything upside down, change the naming of every technology and use the old names with some new things. Of course I’m exaggerating a little here, but some changes are really crucial and can cause confusion. I’m also pretty sure that some of them are not final, so I will probably have to go back to this post in few months to update it.

There are a lot of great blog posts already there but the really short summary of what we know so far:

  1. There will be a common data model for all Microsoft business apps (Dynamics 365 world apps), which is called currently Common Data Model. Basically, we want to have the same Account in CRM as the Account in Talent or Marketing, currently in every system, all the entities do not follow any common schema. CDM specification is held on github and you can check out its current state here: https://github.com/Microsoft/CDM
  2. There will also be a data service that would allow CRUD for all the entities across your Environment. Basically you will reuse the same Account entity in your CRM and in your ERP, so any integrations will not be necessary (or at least fairly easy to develop). This will be called Common Data Service for Apps (and has nothing to do with current CDS)
  3. PowerApps is now becoming a term that includes all customizable business apps  – the old PowerApps from now on called Canvas Apps and applications like Dynamics 365 Customer Engagement are called Model Apps. Both types of apps can use CDS for Apps and CDM. Basically this is our new UI layer over CDS and CDM
  4. The underlying technology for all these new toys is Dynamics 365 CE platform, also known as XRM platform. So if you know Dynamics CRM, you should already be familiar with everything that CDS for Apps, CDM and Model Apps in PowerApps have to offer.
  5. What we currently know as Organization, we should from now on refer to as an Instance. Once the whole new ecosystem is finished, it should be called Environment 

That’s the shortest summary which highlights everything  important from the perspective of technical guys like developers and solution architects. Looks pretty exciting right? At least for Dynamics CRM Developers, who are currently becoming the specialists of the development platform for all new technologies (as a comparison, look at Office 365 applications, where most of applications are SharePoint based).

Ok, so that’s still a theory, we can take that into our minds and wait until the machinery starts running, right? Wrong, we already can start playing with all of that!

I would like to show you how to get started with some new Model App based on CDM.

You will need a Dynamics 365 9.0 environment (can be a trial of course). Log into your Organization and go to the following link:

https://admin.powerapps.com/environments

You should see something like that

1

Now click on New environment button

2

Enter Environment name (for me it’s XRM), choose your region and Environment type (I would not go with Production just yet, but if you want, be my guest). Click Create environment.

3

Ok so we have a new Environment, so in the world that we already know – we have a CRM instance but without any Organization. That’s not very useful, so let’s create a database.

4

Looks like the Organization creator for Dynamics CRM installation, doesn’t it? So we have to put there our desired Currency and Language. I unchecked the sample data, as I would like this app to be as clean as possible. After clicking Create database we will have to wait few minutes:

5

After DB is provisioned we will see something like that:

6

If we will now switch to the old, well-known Dynamics 365 Administration Center, we will see that we have a new CRM organization:

7

Let’s open it! We will see quote “raw” CRM organization:

8

No Sales, Service, Marketing tiles, only Settings. Let’s see what we have in Customizations:

9

You can see only the entities from Common Data Model, so there are only System entities that are required to use all the features of the system (Users, Teams, Views, etc) and some really basic entities (like Account and Contact) – there are no Cases, Opportunities, Leads, Goals etc. Simply a clean XRM platform that we can use to create a totally custom application!

No let’s see the new customizations interface. Open the following link:

https://web.powerapps.com/

10

And on top right corner choose your newly created Environment. Now open your entities:

10.1

Now click on some entity, I chose Account entity:

12

On top pane, you can see all the well-known sections like Fields, Keys, Relationships, Views etc. Let’s create a new field called Short Name

13

After clicking on Save entity, open again Customizations in your empty Organization

14

The field is there!

Once you start playing with all the customizations, you will see that there are still many places where you are redirected to the “old-CRM2011-UI” because there is still no new UI for that, but you can already see that things are heading in the right direction.

For sure Microsoft will need some more time to finish all this new features. Let’s keep our fingers crossed that everything goes as expected, because future looks really exciting!

Better CRM

If you are following the latest news regarding Dynamics 365 ecosystem, you are probably aware of the fact that Microsoft decided to put everything upside down, change the naming of every technology and use the old names with some new things. Of course I’m exaggerating a little here, but some changes are really crucial and can cause confusion. I’m also pretty sure that some of them are not final, so I will probably have to go back to this post in few months to update it.

There are a lot of great blog posts already there but the really short summary of what we know so far:

  1. There will be a common data model for all Microsoft business apps (Dynamics 365 world apps), which is called currently Common Data Model. Basically, we want to have the same Account in CRM as the Account in Talent or Marketing, currently in…

View original post 754 more words

Setting up a visual hierarchy on a custom entity

Hierarchy visualisation can be configured in MSD 365, its pretty easy. Here are the steps for it. Create a lookup field, while creating it keep Hierarchical = Yes Keep it on form to select parent record  Now go to Customisation >> Your Entity >> Hierarchy Settings Click on New >> Name = name the hierarchy … Continue reading Setting up a visual hierarchy on a custom entity

Configure the schedule board for resource availability

The Dynamics 365 for Field Service schedule board provides an overview of resource availability and bookings you can make. Before you use the schedule board, it is important to set up the views and filters to your preference. Applicable to Dynamics 365 (online) ==> Field Service, version 9.x Important To use the schedule board booking functionality, … Continue reading Configure the schedule board for resource availability

Schedule anything with Universal Resource Scheduling

Schedule anything in Dynamics 365 using Universal Resource Scheduling. You can enable scheduling for any entity including custom entities. For example, you can enable scheduling for the opportunity form and schedule marketing visits for your opportunities. You can also do this for the case form and schedule time to work on cases. This is applicable … Continue reading Schedule anything with Universal Resource Scheduling