Practice Labs

81059 Customizing Dynamics 365 for Sales and Service
Before you begin

All of the labs used in this course have been designed to work with Dynamics 365 Online. We recommend that prior to
doing the labs that you sign up for a Dynamics 365 Online Trial organization. The Specific steps on how to signup are
located below.
Obtaining a Dynamics 365 Trial

1. Open a web browser and navigate either search for “Dynamics 365 Online Trial”, or navigate directly to the trial
address. In the United States, the address is https://www.microsoft.com/en-us/dynamics/crm-free-trial-
overview.aspx
2. For purposes of this training, we recommend that you Do Not Click the Try it Free button:
a. This is for the Dynamics 365 Concierge Service, in which an agent will guide you through the application and
specific Scenarios.
b. It’s a wonderful service, but your organization will not be set up immediately. For training purposes we want it
setup right away.
3. Locate and click, No thanks, I’ll get started on my own. (Located about half way down the Page)
a. Fill out all of the Registration information and click Next.
i. Note: All this information is required
4. Next you will be setting up the primary account and organization information for you trial organization. Be sure
to take note as you will need this later
a. Enter a username that you want to use as the primary user account for your trial
b. Enter a name that you want to use for you trial organizations name
i. The name you choose will be validated to determine if it is available
c. Create and Confirm a password that you want to use from your Trial Organization
d. Click Next
5. You will need to Prove you are not a robot by entering in a confirmation code that can be either sent to you via a
Text or Phone call.
a. Choose either Text or Call
b. Enter your full 10 digit phone number
c. Click the Text me or Call me Link
d. After you receive your Code, enter it into the Verification Code Field
e. Click Create my Account
6. As your Account is being created you will be sent to a screen that will provide you with the following
information:
a. The Office 365 sign-in page: https://portal.office.com
b. Your user ID: Ex. Someone@name.onmicrosoft.com.
7. Once everything completes, click the You’re ready to go… link

8. You will need to provide some finial details for your trial organization,
9. Accept the defaults, and click Finish
10. You will be presented with a Getting Setup Page.
11. Once complete you will be given the Link to your Dynamics 365 Trail organization.
a. We recommend bookmarking it as you will be using it often through the rest of the course.
Module 2: Introduction to Dynamics 365 Solutions
Practice 2.1: Create a Solution
Scenario
As a member of the Microsoft Dynamics 365 project team for Adventure Works Cycles, you have to make a series of
modifications to the system. The modifications will help the New Product Development (NPD) team manage its
processes. You have to create several new entities, add fields to store specific data that is required by the NPD team,
and create forms and views that the NPD team can use to work with its new records.
Exercise Scenario
Before you start to make changes, you want to create a new Solution to contain your customizations. When you have
completed the necessary configuration, you can export these changes as a solution package to import into another
Microsoft Dynamics 365 Organization. By doing this, users can test the changes that you created and provide feedback
before you deploy to the live production system. You also want to easily identify these changes in the future as having
originated from the NPD team. Therefore, you will create a new Publisher to make sure that the new components have
an appropriate prefix.
After you create your Solution, you must add some entities that you think might require some customization to meet the
business requirements that you received. Make sure that you do not include anything in the Solution that you have not
modified, because you do not want your Solution to become larger than is necessary, or include unexpected changes
that are made by someone else.
Note: The Solution that you create in this exercise is used in all remaining labs throughout the course as a container to
perform all customizations. We recommend that you keep the Solution window open throughout so that it is easy to switch between
your configuration environment and the main navigation window to view and test your changes as you progress. By the end of the
course you will have a Solution that contains all the components and changes that you have made in every module.
High Level Steps

1. Create a new Solution named “NPD and Feedback.”
2. Create a Publisher named NPD and Feedback, and use the prefix npd.
3. Add Account, Contact and Campaign entities to the Solution.
4. Remove the Campaign entity from the Solution.
5. Add the Sales Manager Security Role to the Solution.
Detailed Steps
1. Create a new Solution named “NPD and Feedback.”
a. If necessary open an internet browser and navigate to your trial organization. Ex.
https://orgname.crm.dynamics.com.
b. In the navigation bar, click on the Main button, and then click Settings.
c. Select Solutions under the Customizations heading.
d. In the menu bar, above the list of Solutions, click New. The Solution: New Solution form will be
displayed.
e. Enter NPD and Feedback as the Display Name.
f. Enter 1.0.0.0 as the Version Number.
2. Create a Publisher named NPD and Feedback, and use the prefix npd.
a. In the Solution: New Solution form, in the Publisher field, click the lookup icon.
b. Click Look Up More Records.
c. In the Look Up Record dialog box, click New.
d. Enter AWC NPD and Feedback for the Display Name.
e. Enter npd for the Prefix (notice this converts to lowercase letters however you type it).
f. In the toolbar, click Save and Close.
g. In the Look Up Record dialog box, click Add.
h. In the Solution: New Solution form, in the toolbar, click Save.
3. Add Account, Contact and Campaign entities to the Solution.

a. In the Solution: NPD and Feedback form, in the solution explorer at the left side, click Entities.
b. In the menu bar, at the top of the (empty) list of entities in the Solution, click Add Existing.
c. In the Select solution components dialog box, notice that the Component Type is filtered to Entity only.
d. Click to the left side of the entities Account, Campaign and Contact to enter a check mark next to each.
e. Click OK.
f. You should now be prompted to add specific Entity Assets, for each of the Entities that you added to the
solution.
g. Onn the Select Entity Assets for the Account Entity, check the Add All Assets box.
h. Click Next
i. Check the Add All Assets box for the Case Entity.
j. Click Next
k. Check the Add All Assets box for Contact Entity
l. Click Finish
m. Click the Save button to save the solution and leave it open.
4. Remove the Campaign entity from the Solution. (Sometimes you may find that you have a component that is no
longer needed in a solution. In this case let’s pretend that you realized that you do not need the Campaign entity)
a. In the Solution: NPD and Feedback form, in the component list, select the Campaign entity.
b. In the menu bar, at the top of the component list, click Remove.
5. Add the Salesperson Security Roles to the Solution.

a. In the solution explorer pane on the left, click Security Roles
b. On the menu bar at the top of the list of Security Roles in the Solution (none at the moment), click Add
Existing.
c. In the Select solution components dialog box, select the Salesperson role then click OK.
d. Leave the Solution window open for use in later labs.
Module 3: Customizing Entities and Fields
Practice 3.1: Create Custom Entities
Scenario
In this exercise, you will create and test two new entities, Idea and Prototype.
Lab Setup
Important: Before you perform this lab, it is recommended that you complete Module 2 “Introduction to Solutions”
Exercise Scenario
Adventure Works Cycles wants to track suggestions that are made by employees and customers as Ideas by using
Microsoft Dynamics 365. When an Idea is submitted, the Adventure Works Cycles New Product Development (NPD)
team will consider the feasibility of the Idea. Ideas that might be potentially worthwhile are proposed as Prototypes for
testing and market research.
In this exercise, you will create a custom entity that is named Idea. The properties of the Idea entity should be
configured as follows:
Idea Prototype
Property Setting Property Setting
Display Name Idea Display Name Prototype
Plural Name Ideas Plural Name Prototypes
Ownership User or Team Ownership User or Team
Display Areas Sales, Service, Marketing Display Areas Service, Marketing
Connections Not Checked Notes Enabled
Mail Merge Not Checked Activities Enabled
Connections Enabled
Queues Enabled
After you create the entities, The Salesperson Security Role should be modified to grant all privileges to both entities at
the user level except for Read and Append To privileges. These should be at the organization level.
Task 1: Create the Idea and Prototype Entities and Assign Security Role Privileges
High Level Steps

1. Create the Idea entity in the NPD and Feedback Solution by using the requirements in the scenario.
2. Create the Prototype entity in the NPD and Feedback Solution by using the requirements in the scenario.
3. Configure the Salesperson Security Role as described in the exercise scenario.
Detailed Steps
1. Create the Idea entity in the NPD and Feedback Solution by using the requirements in the scenario.
a. Switch to the NPD and Feedback Solution if you still have the window open. Otherwise navigate to
Settings > Solutions and double-click the Solution to open it.
b. In the solution explorer, click Entities.
c. On the menu bar at the top of the list of entities, click New.
d. In Display Name, enter Idea.
e. In Plural Name, enter Ideas.
f. Make sure that the Ownership property is set to User or Team.
g. In the Areas that display this entity section, select Sales, Service and Marketing.
h. In the Communication & Collaboration section deselect the check boxes for Connections and Mail
Merge.
i. All other settings should be left at their defaults.
j. Click Save and Close.
2. Create the Prototype entity in the NPD and Feedback Solution by using the requirements in the scenario.
a. With the NPD and Feedback Solution window still open, in the solution explorer click Entities.
b. On the menu bar at the top of the list of entities, click New.
c. In Display Name, enter Prototype.
d. In Plural Name, enter Prototypes.
e. Make sure that the Ownership property is set to User or Team.
f. In the Areas that display this entity section, select Service and Marketing.
g. In the Communication & Collaboration ensure that Notes, Activities, Connections and Queues are
enabled.
h. All other settings should be left at the defaults.
i. Click Save and Close.
3. Configure the Salesperson Security Role as described in the exercise scenario.

a. In the solution explorer, click Security Roles.
b. Double-click the Salesperson Security Role to open it.
c. Click the Custom Entities tab.
d. Click directly on the Idea entity name until all privileges are set to User level.
e. Click the Read privilege for Idea until it is set to Organization level.
f. Click on the Prototype entity name until all privileges are set to User level.
g. Click the Read privilege for Prototype until it is set to Organization level.
h. Click the Append To privilege for Prototype until it is set to Organization level
j. On the Command Bar on the Solution, click Publish All Customizations
k. Leave the Solution window open for later labs.
Practice 3.2: Create a Custom Activity Entity
Scenario
Adventure Works Cycles wants to record structured feedback from employees and customers about various processes
and interactions, such as placing an order, contacting support or attending an event. By creating a custom activity entity
named Feedback this can be associated with any record that supports activities, instead of having to create several
specific relationships to individual entities.
Lab Setup
Important: Before you perform this lab, you must have created the Idea and Prototype entities that were created in the
previous exercise. Without them you will encounter problems. It is also highly recommended that you have completed
all previous labs as well.
Exercise Scenario
In this exercise, you will create and test a custom activity entity named Feedback.
You will test the entity by creating new Feedback activities for the record named “Test prototype” that you created in
the earlier exercise.
Task 1: Create the Feedback Entity

High Level Steps
1. Create the Feedback entity as a custom activity in the NPD and Feedback Solution.
2. All Data Services and Outlook & Mobile options should be disabled.
3. Test the Feedback Entity.
Detailed Steps
1. Create the Feedback entity as a custom activity in the NPD and Feedback Solution.
a. Switch to the NPD and Feedback Solution by using the Windows taskbar.
b. In the solution explorer click Entities.
c. On the menu bar at the top of the list of entities, click New.
d. In the Display Name field, enter Feedback.
e. In the Plural Name field, enter Feedback.
f. IMPORTANT: (If you skip this, the Activity Entity will not function correctly). Select the check boxes
Define as an activity entity and Display in Activity Menus.
i. Notice that Ownership is set to User or Team and cannot be changed.
g. In Data Services and Outlook & Mobile sections clear any options that are checked (the Offline
capability for CRM for Outlook cannot be cleared.)
h. Click Save and Close to close the new entity form.
i. Click Publish All Customizations
j. Keep the Solution window open for later labs.
2. Test the Feedback Custom Activity.

a. Switch back to your CRM organization
b. Navigate to the Prototype entity by selecting Main > Service > Prototypes
c. If you have a prototype record, Double-click the record to open it.
i. If you do not have a Prototype Record:
ii. On the Active Prototypes view, click the New button.
iii. In the Name field, enter Test Prototype.
iv. Click Save, to save the record and keep it open.
d. In the Activities pane in the middle of the form, select the word ACTIVITES if not already
selected
e. Click the Add more activities button (…), Select Feedback. (You can also do this from the
command bar by clicking the Ellipsis button > Other Activities > Feedback.)
f. Enter Feedback 1 into the Subject field.
g. On the command bar click Save.
h. To return to the Prototype form, in the Regarding field, click the link to the Test prototype
record.
i. In the Activities pane in the middle of the form, confirm that the new Feedback1 record is
shown..
j. In the Activities pane in the middle of the form, click the Add more activities button again, and
then click Feedback.
k. Enter Feedback 2 into the Subject field.
l. On the command bar click Save, and then click Mark Complete.
m. Confirm that the completed Feedback record is shown on the Prototype in the Activities area of
the social pane. Note: the completed activity has a gray background.
Practice 3.3: Create Custom Fields
Exercise Scenario
In the last Exercise you created a custom entity called Idea. Adventure Works Cycles require additional fields to be
added to the entity as follows:
Field Name Data Type Additional requirements

Detailed Description Multiple lines of text Business Required
Target Market Size Whole number Business Recommended
Minimum value 0
Maximum value 1,000,000,000
Your task is to create these two fields within the Idea entity. In the module Customizing Forms you will add the fields to
the form.
High Level Steps

1. Access the Idea entity within the Solution.
2. Add the Detailed Description field according to the scenario.
3. Add the Target Market Size field according to the scenario.
Detailed Steps
1. Access the Idea entity within the Solution.
a. If your NPD and Feedback solutions is not open, using the navigation bar, click the Main Button >
Settings > Solutions.
b. Open the NPD and Feedback Solution
c. Click Entities.
d. Expand the Idea entity.
2. Add the Detailed Description field according to the scenario.

a. Within the Idea entity click Fields.
b. On the toolbar click New.
c. Complete the New Field form as follows:
i. In the Display Name field enter Detailed Description.
ii. Set the Field Requirement property to Business Required.
iii. In the Description field enter the text: The detailed description of the idea.
iv. Set the Data Type field to read Multiple Lines of Text.
d. Click Save and Close
3. Add the Target Market Size field according to the scenario.

a. Within the Idea entity click Fields.
b. On the toolbar click New.
c. Complete the New Field form as follows:
i. In the Display Name field enter Target Market Size.
ii. Set the Field Requirement property to Business Recommended.
iii. In the Description field enter the text: The size of the target market.
iv. Set the Data Type field to read Whole Number.
v. Set the Minimum Value to 0.
vi. Set the Maximum Value to 1,000,000,000.
d. Click Save and Close.
Don’t worry about adding the fields to the form or publishing your customizations. We will be adding additional fields in
the next module, so we will wait until we have more information to display.
Module 4: Additional Field Customizations
Practice 4.1: Create and Modify a Global Option Set
Lab Setup
Important: Before you perform this lab, you must have completed all of labs in Module 2 “Intro to Solutions” and
Module 3 “Customizing Entities and Fields”. You will be building on the Idea and Prototype entities that were created in
the previous exercise. Without them you will encounter problems. It is also highly recommended that you have
completed all previous labs as well. You can install the NPDandFeedback_1_5_0_1.zip solution that was included in your
course materials. It contains all of the customizations made prior to this module.
Scenario
Adventure Works Cycles wants to be able to track the satisfaction of their customers. Initially they only require to have
this information on the feedback entity but eventually they may want to capture this on other entities. They require a
new Option Set field called Satisfaction Rating to be created on the Feedback form.
The field should be configured as follows:
Field Name Requirements

Rating Business Required
Use a Global Option Set called “Rating”.
Option Set values:
 Very Happy
 Happy
 Neutral
 Unhappy
 Very Unhappy
Default value: Neutral.
You are required to perform the following tasks:

1. Create the Global Option Set.
2. Create the Satisfaction Rating field within the Feedback entity.
3. Add the Satisfaction Rating field to the form.
4. Test that the field works as expected.
Exercise Scenario
In this exercise you will create a Global Option Set configured as follows:
Display Name Values
Rating Very Happy
Happy
Neutral
Unhappy
Very Unhappy
You will then create an Option Set field within the Feedback entity configured as follows:
Display Name Field Requirement Option Set Default Value
Rating Business Required Ratings Neutral
Once complete, you will add the Satisfaction Rating field to the Feedback form then test its behavior.
Task 1: Create a Global Option Set Called Ratings
High Level Steps

1. Create a new Global Option Set called Ratings.
2. Create a Satisfaction Rating Option Set field on the Feedback Entity.
Detailed Steps
1. Create a new Global Option Set called Ratings.
a. In CRM Open the NPD and Feedback Solution by clicking the Main button > Settings > Solution
b. Click Option Sets.
c. On the toolbar click New.
d. Enter Ratings into the Display Name field.
e. In the Description field enter Customer Satisfaction Ratings.
f. In the Options field click the Add button (Green Plus Sign).
g. In the Label field enter Very Happy.
h. Click the Add button.
i. In the Label field enter Happy.
j. Click the Add button.
k. In the Label field enter Neutral.
l. Click the Add button.
m. In the Label field enter Unhappy.
n. Click the Add button.
o. In the Label field enter Very Unhappy.
p. Click Save and Close.
2. Add a new Option Set Field to the Feedback entity.

a. In the NPD and Feedback Solution, expand Entities.
b. Expand the Feedback entity.
c. Click Fields.
d. On the toolbar click New.
e. In the New Field form, enter Satisfaction Rating into the Display Name field.
f. Set the Field Requirement to Business Required.
g. In the Data Type field select Option Set.
h. In the Use Existing Option Set field select Yes.
i. In the Option Set field select Ratings.
j. In the Default Value field select Neutral.
k. Click Save and Close.
Practice 4.2: Create a Calculated and Rollup fields
Exercise Scenario
It is important for Adventure Works Cycles to be able to see how many feedbacks have been submitted for a specific
prototype. In addition some feedbacks may have costs associated with them. Adventure Works, wants to potentially be
able to compare cost with budget on a specific prototype.
High Level Steps

1. Create a Rollup Field that counts the total number of feedbacks for a Prototype.
2. Add a Cost field to the Feedback Entity
3. Add a Budget Field to the Prototype Entity
4. Create a Total Cost Rollup field on the Prototype entity to Sum the Cost field of all attached Feedbacks.
Detailed Steps
3. Create the Total Feedbacks Rollup Field.
a. In CRM Open the NPD and Feedback Solution by clicking the Main button > Settings > Solution
b. Click Fields.
c. On the toolbar click New.
d. Enter Total Feedbacks into the Display Name field.
e. Change the Data Type to Whole Number.
f. Select Rollup for Field Type.
g. Click Edit. (Note that this will save the field automatically)
h. The Total Feedbacks Rollup Field window will display.
i. Leave the Source as Prototype and Use Hierarchy as No.
j. Under Related Entity, click Add Related Entity
k. Choose Feedbacks (Regarding).
l. Click the Checkmark button to accept the Condition.
m. Under Aggregation, click Add Aggregation.
n. For Aggregate Function, select Count.
o. Aggregated Related Entity field will default to Feedback.
p. Click the Checkmark button to accept the Aggregation.
q. Click Save and Close to close the Rollup Field editor.
r. Click Save and Close to close the Total Feedbacks Rollup Field
4. Add a Cost field for the Feedback Entity

b. Expand the Feedback entity.
c. Click Fields.
e. In the Display Name field, enter Cost.
f. Currency
g. Click Save and Close
5. Add a Budget field on the Prototype Entity

b. Expand the Prototype entity.
c. Click Fields.
e. In the Display Name field, enter Budget.
f. Currency
g. Click Save and Close
6. Create a Total Cost Rollup field on the Prototype entity

b. Expand the Prototype entity.
c. Click Fields.
e. In the New Field form, enter Total Cost into the Display Name field.
f. In the Data Type field select Currency.
g. Set the Field Type to Rollup.
h. Click Edit. (Note that this will save the field automatically)
i. The Total Cost Rollup Field window will display.
j. Leave the Source as Prototype and Use Hierarchy as No.
k. Under Related Entity, click Add Related Entity
l. Choose Feedbacks (Regarding).
m. Click the Checkmark button to accept the Condition.
n. Under Aggregation, click Add Aggregation.
o. For Aggregate Function, select Sum.
p. Aggregated Related Entity field will default to Feedback (Cost).
q. Click the Checkmark button to accept the Aggregation.
r. Click Save and Close to close the Rollup Field editor.
s. Click Save and Close to close the Total Feedbacks Rollup Field
Practice 4.3: Configure Field Security

Scenario
Ben Burton, the Marketing Manager at Adventure Works Cycles, wants to track the budget allocated to a Prototype. This
will depend on the expected market size, estimated feasibility of developing the prototype into a finished product and
other factors.
You must create a new field named Budget, and apply Field Security to it. You must configure Field Security Profiles to
control access to this to meet the business requirements. All users who work in the Product Development Team need to
be able to view the value of the Budget field so they can make sure expenditure remains within the limit that has been
set. Only Sales Managers must be able to change the value.
Lab Setup
Before you perform this lab, you must have created the Budget field on the Prototype entity from the previous exercise.
High Level Steps

1. Enable Field Security for the Budget field of the Prototype entity in the NPD and Feedback Solution.
2. Create and configure a Field Security Profile to allow Read access to the Budget field for the Product
Development Team.
3. Create and configure a Field Security Profile to allow Update access to the Budget field for a new Team named
Sales Managers.
Detailed Steps
1. Enable Field Security for the Budget field of the Prototype entity in the NPD and Feedback Solution.
a. Switch to the NPD and Feedback Solution if it is still open. Otherwise Click the Main button > Settings >
Solutions and double-click the NPD and Feedback Solution to open it.
b. In the solution explorer, expand Entities.
c. Expand the Prototype entity.
d. Click Fields.
e. In the list of fields for the Prototype entity, double-click to open the Budget field.
f. In Field Security, select Enable.
g. On the toolbar, click Save and Close.
h. Select the Prototype Entity
i. Click the Publish Button
2. Create and configure a Field Security Profile to allow Read access to the Budget field for the Product
Development Team.
a. In the NPD and Feedback Solution, at the bottom of the solution explorer, click Field Security Profiles.
b. In the menu bar, click New.
c. In the New Field Security Profile form, in Name, enter NPD Budget Read Access.
d. On the toolbar, click Save.
e. In the navigation pane to the left of the window, click Teams.
f. In the menu bar, click Add.
g. In the Look Up Records dialog box, click new and create a Team with the name of the Product
Development.
h. Save the Team
i. In the Product Development Team form, in the Team members section, click + (Add User record).
j. In the lookup control that is displayed, select Ben Burton (Or any User that you want if Ben does not exist).
k. Close the Product Development Team window.
l. With the Product Development team record selected, click Select, and then click Add.
m. In the navigation pane, click Field Permissions. A list of all fields in the system that have field security
enabled is displayed.
n. Double-click the Budget field, or select it and then click Edit.
o. In Allow Read, select Yes. Leave the other options as No.
p. Click OK.
q. On the toolbar, click Save and Close.
3. Create and configure a Field Security Profile to allow Update access to the Budget field for a new Team named
NPD Managers.
a. In the NPD and Feedback Solution, using solution explorer, navigate to Field Security Profiles if necessary.
b. In the Field Security Profiles menu bar, click New.
c. In the New Field Security Profile form, in Name, enter NPD Managers Budget Update Access.
d. On the toolbar, click Save.
e. In the navigation pane to the left of the window, click Teams.
f. In the menu bar, click Add.
g. In the Look Up Records dialog box, at the lower left click New.
h. In the New Development Team form, in Name enter NPD Managers.
i. In Administrator, select your User Account.
j. On the command bar, click Save.
k. In the Look Up Records dialog box, click the name of the NPD Managers Team to open the Team record.
l. In the NPD Managers Team form, in the Team members section, click + (Add User record).
m. In the lookup control that is displayed, select Ben Burton (Or any user if Ben does not exist).
n. In the Team members section, click + (Add User record).
o. In the lookup control that is displayed, select Ben Burton (Or any user if Ben does not exist).
p. Close the NPD Managers Team window.
q. In the Look Up Records dialog box, click Add.
r. In the navigation pane, click Field Permissions. A list of all fields in the system that have field security
enabled is displayed.
s. Double-click the Budget field, or select it and then click Edit.
t. Set Allow Read, Allow Update, and Allow Create to Yes.
u. Click OK. On the toolbar, click Save and Close.
Module 5: Relationships
Practice 5.1: Create a 1:N Relationship
Exercise Scenario
You must create a 1:N relationship between the Idea and Prototype entities and modify it to meet the
requirements of the NPD team. To prevent Prototype records being created without an Idea record, you will
create a lookup field on Prototype named “Originating Idea”, make this Business Required and add it to the
Prototype form.
To make sure that Prototypes are assigned correctly when an Idea is assigned, you will configure the
relationship behavior to configurable cascading and change the assign rule to Cascade User-Owned.
To prevent Ideas being deleted if they have related Prototypes, change the delete rule to Restrict.
You must create some records and test your configuration changes.
Lab Setup
Before you perform this lab, it is recommended that you have completed all the previous labs. You will need
the Idea and Prototype entities in order to complete this lab.
Create a 1:N Relationship

High Level Steps
1. Create a 1:N relationship between the Idea and Prototype entities.
Detailed Steps
1. Create a 1:N relationship between the Idea and Prototype Entities.
a. If necessary open the NPD and Feedback Solution, by clicking the Main button > Settings > Solutions
and double-click the Solution to open it.
b. In the solution explorer, expand Entities, and then expand Idea.
c. Under the Idea entity, click 1:N Relationships.
d. On the action bar, click New 1-to-Many Relationship.
e. In the Relationship form, in the Related Entity list select Prototype.
f. In Name, Highlight npd_ before Idea and press delete.
g. Highlight _npd before Prototype and press delete.
h. The Name should read npd_idea_prototype. (This includes the Publisher Prefex)
i. In the Lookup Field section, enter Originating Idea in Display Name.
j. In the Field Requirement list, select Business Required.
k. In the Type of Behavior list, select Configurable Cascading.
l. In the Assign list, select Cascade User-Owned.
m. In the Delete list, select Restrict.
n. On the toolbar, click Save and Close.
Practice 5.2: Create a N:N Relationship
Exercise Scenario
When ideas are submitted, Adventure Works Cycles need to identify competitors who are already in that area
of the market, to help assess the feasibility of competing effectively against them. By tracking Ideas against
Competitors, this will help steer product development in the most viable direction, for example whether
innovation, price, quality or other factors are more likely to make a new product successful.
You must create a many-to-many relationship between the Idea entity you created in the “Customizing
Entities” module and the built-in Competitor entity, and test that it works correctly.
Create a N:N Relationship
High Level Steps

1. Create a N:N relationship between the Idea and Competitor entities.
Detailed Steps
1. Create a N:N relationship between the Idea and Competitor entities.
a. Ensure you still have NPD and Feedback solution open.
b. In the solution explorer, expand Entities then expand Idea.
c. Under the Idea entity click N:N Relationships.
d. On the action bar, click New Many-to-Many Relationship.
e. In the New Relationship form, in the Current Entity section (Idea), set the Display Option to Use Plural
Name.
f. In the Other Entity section, in the Entity Name list select Competitor.
g. In the Other Entity section, in the Display Option list select Use Plural Name.
h. On the toolbar, click Save and Close to return to the Solution.
i. Leave the NPD and Feedback Solution window open for later labs.
2. Link an Idea to an existing Competitor.

a. Switch to the main navigation window.
b. Navigate to Sales > Competitors.
c. On the command bar, click New.
d. In the New Competitor record, in Name enter Wingtip Toys.
e. On the command bar, click Save.
f. Navigate to Marketing > Ideas.
g. Click New
h. Enter New range of helmets in the Name field.
i. Click Save
j. On the navigation bar, click or point to the drop-down arrow to the right of New range of helmets then
click Competitors.
k. Below the view label Competitor Associated View, on the command bar, click Add Existing Competitor.
l. In the lookup entry which appears in the list, enter Wingtip and press the Tab key.
3. Link an Idea to a new Competitor.
a. With the New range of helmets Idea still open, click Add Existing Competitor. A lookup control is
displayed in the list.
b. Click the lookup icon at the right side of the lookup control, and then click Look Up More Records.
c. In the Look Up Records dialog box which appears, at the lower left corner click New.
d. On the New Competitor form, enter the name Wide World Importers, then click Save.
e. In the Look Up Records dialog box, click Add.
f. Click Wide World Importers in the list of Competitors to open it.
g. On the navigation bar, click or point to the drop-down arrow to the right of Wide World Importers then
click Ideas.
h. Verify that New range of helmets is shown in the list of associated Ideas, because the N:N relationship is
symmetrical.
Practice 5.3: Customize Relationship Mappings

High Level Steps
1. Open the 1:N relationship between Idea and Prototype.
2. Create a mapping between the Owner fields of both entities.
3. Test the field mapping by creating a Prototype from an Idea.
Detailed Steps
1. Open the 1:N relationship between Idea and Prototype

a. If necessary open the NPD and Feedback by clicking the Main button > Settings > Solutions and double-
click the NPD and Feedback Solution to open it.
c. Under the Idea entity, click 1:N Relationships
d. Find the relationship with Prototype as the Related Entity (you can sort this column by clicking the
heading).
e. Double-click to open the relationship.
2. Create a mapping between the Owner fields of both entities.

a. In the Idea to Prototype relationship form, in the navigation pane, click Mappings.
b. On the menu bar at the top of the list of mappings, click New.
c. In the Source Entity Fields list, select ownerid.
d. In the Target Entity Fields list, select ownerid.
e. Click OK.
f. Click New.
g. In the Relationship form, click Save and Close.
h. Leave the NPD and Feedback Solution window open for later labs.
3. Test the field mapping by creating a Prototype from an Idea.

a. Switch to the main application window by using the Windows taskbar.
b. Navigate to Microsoft Dynamics CRM > Marketing > Ideas.
c. Open the New range of helmets Idea. Note the current owner of the record.
d. On the navigation bar, click or point to the drop-down arrow to the right of New range of helmets then
click Prototypes.
e. Below the view label Prototype Associated View, on the command bar, click Add New Prototype.
f. In the New Prototype form, in Name, enter Off-road helmet with headlights.
g. Verify that the owner of the Prototype record matches the owner of the Idea.
h. Click Save, then close the Prototype record window.
Practice 5.4: Create a Hierarchical Relationship
Scenario
There are many times with Adventure Works, has prototypes that actually fall under a specific master prototype. They
may have a special helmet design, but may test multiple versions of the prototype with different straps or padding. They
want to be able potentially add sub-prototypes under master records in certain cases.
High Level Steps

1. Create a New 1:N Self Referential on the Prototype Entity to be used for Hierarchy Data.
2. Define the Hierarchy Setting for the Prototype Entity.
Detailed Steps
1. Create a New 1:N Self Referential on the Prototype Entity to be used for Hierarchy Data
a. If necessary open the NPD and Feedback by clicking Main button > Settings > Solutions and double-click
the NPD and Feedback Solution to open it.
b. In the solution explorer, expand Entities then expand Prototype.
c. Under the Prototype entity, click 1:N Relationships
d. Find the relationship with Prototype as the Related Entity (you can sort this column by clicking the
heading).
e. Click the New 1-to-Many Relationship button.
f. The Primary Entity will be set as Prototype. (You will not be able to change it)
g. From the Dropdown menu on Related Entity, choose Prototype
h. Edit the relationship name to show npd_prototype_prototype (Including the prefix)
i. In the Hierarchical field, select Yes.
j. Enter Master Prototype in the Display Name field.
k. Click Save and Close
2. Define the Hierarchy Setting for the Prototype Entity.

a. In the NPD and Feedback Solution, expand the Prototype Entity if necessary.
b. Click Hierarchy Settings.
c. Click the b button
d. In the Name field, enter Prototype
e. Next to Default Quick View Form, click Create New.
f. Click the Form Properties button
g. Enter Basic Prototype in the Form Name field
h. Click OK
i. Under Field Explorer, double click the following fields to add them to the Form.
i. Name, Budget, Owner, and Originating Idea.
j. Click Save and Close
k. Verify that Basic Prototype is listed in the Default Quick View Form
l. The Hierarchical Relationship field will auto-populate with the Hierarchical Relationship you created in
the previous task.
m. Click Save and Close
n. Leave the NPD and Feedback Solution window open for later labs.
o.
Module 6: Customizing Dynamics 365 Forms
Practice 6.1: Add Fields to Forms
Scenario
You need to continue the configuration of the Idea entity by adding some of the fields created previously to the form,
and modify the layout to organize these logically. You also need to modify the Prototype form, and add some additional
fields at the same time. The Prototype form also needs some changes to the layout to present the information as clearly
as possible.
Lab Setup
Before doing this lab you need to have completed the all of the Previous Labs to this Point including Module 3
“Customizing Entities and Fields”, Module 4 “Additional Field Customizations”, and Module 5 “Relationships”.
Exercise Scenario
In this exercise you must format an existing tab and section on the Idea Information form, add two existing fields to the
form and modify the layout of one of the fields.
The specific requirements are outline in the High level Steps. You must also add a new section to the Prototype
Information form, create two new fields and add these to the new section. The two new fields must have the properties
shown in the following table.
Field Name Properties

Planned Completion Type: Date
Format: Date only
Task 1: Customize the Idea and Feedback Forms and Add Existing Fields
High Level Steps

1. Open the Idea form called Information from NPD and Feedback solution.
2. Modify the General tab columns to 50% of the width for each, and modify the General section to have two
columns.
3. Modify the Name field to span two columns, add the Target Market Size and Description fields to the General
section and modify the Description field to span two columns and five rows.
4. Add a Sub-grid to the Idea form that will display related Prototypes.
5. Add the Cost and Satisfaction Rating field to the Feedback form.
Detailed Steps
1. Open the Idea form called Information from NPD and Feedback solution.
a. If the NPD and Feedback Solution is not already open, click the Main button > Settings > Solutions and
double-click the NPD and Feedback solution to open it.
c. Under the Idea entity click Forms.
d. Click Forms.
e. Double-click the Information form with a Form Type of Main.
2. Modify the General tab columns to 50% of the width for each, and modify the General section to have two
columns.
a. Double-click the General tab or click to select it (blue box will appear around the entire tab) and click
Change Properties.
b. In the Tab Properties dialog box, click the Formatting tab.
c. In the Layout section, under Two Columns, select the two column icon on the furthest to the left. Note that
the column widths change to 50% each.
d. Click OK.
e. Double-click the General section.
f. In the Section Properties dialog box, click the Formatting tab.
g. In the Layout section, select Two Columns.
h. Click OK.
3. Modify the Name field to span two columns, add the Target Market Size and Description fields to the General
section and modify the Description field to span two columns and five rows.
a. Double-click the Name field on the form.
b. In the Field Properties dialog box, click the Formatting tab.
c. In the Layout section, select Two columns to span both columns of the containing section. Note that the
options for Three and Four columns are unavailable. Click OK.
d. In the Field Explorer pane, in the Filter list, select Custom Fields.
e. In Field Explorer pane Double click Target Market Size field. Drag it next to Owner.
f. Double click the Target Market Size field.
g. In the Field Properties dialog box, on the Display tab, change the Label to Target Market (delete the word
“Size”). Click OK.
h. In Field Explorer pane Double click Detailed Description field. Drag it under Owner.
i. Double-click the Description field.
j. In the Field Properties dialog box, click the Formatting tab.
k. In the Layout section, select Two columns.
l. In the Row Layout section, in Number of Rows, enter 5.
m. Click OK.
n. Next you will now create a new Section on the General Tab called Idea Details.
o. On the form editor ribbon, click INSERT
p. Click the arrow below Section on the far left hand side of the ribbon
q. Select One Column
r. Locate the new section that was added to the form just below the Detailed Description field.
s. Double-click the section to open the section properties.
t. Change the Name to Idea_Details (Note: that the name cannot include spaces).
u. Change the Label to Idea Details (The Label can include spaces).
v. Select the two checkboxes Show the label of this section on the form and Show a line at the top of the
section
w. Click OK.
x. In the Field Explorer, click the Target Market field and drag it into the Idea Details section, just below the
Detailed Description field.
4. Add a Sub-Grid to the Idea Entity to show related Prototypes.

a. On the Ribbon, select Insert, click the arrow below Section, and select One Column.
b. Double-click the new section to open the Properties.
c. Enter Prototypes for the Name and Label.
d. Check both the Show the label of this section on the Form and Show a line at the top of the section boxes.
e. Click OK
f. On the Insert ribbon, click the Sub-Grid button
g. Enter Prototypes for the Name
h. In the Data Source section, select Prototypes (Originating Idea) from the Entity Dropdown.
i. Verify that Only Related Records is selected for Records
j. Click Set
k. On the ribbon, click the Home tab then click Save.
l. Click Publish.
m. Click Save and Close.
n. Keep the Solution window open for the next task in this lab exercise.
5. Add the Cost and Satisfaction Rating fields to the Feedback Activity Entity
a. In the NPD and Feedback solution, expand the Feedback entity.
b. Click Forms.
c. Double-Click the Main Information form to open it.
d. In the Field Explorer pane, change the Filter to Custom Fields.
e. Double-click the Cost field to add it just below the Regarding field.
f. Double-click the Satisfaction Rating field to add it just below the Cost Field.
g. Click Save
h. Click Publish
i. Click Save and Close
Task 2: Customize the Prototype Form and Add New Fields
High Level Steps

1. Open the Prototype form called Information.
2. Add two new fields to the Prototype entity.
3. Create a new one column section called Planning.
4. Add the Planned Completion, Currency and Budget fields to the form.
5. Configure the Originating Idea field to be read-only.
6. Add the Owner field to the form header.
7. Add the Modified By and Modified On fields to the form footer.
8. Test your changes to both entities by creating some Prototypes from an existing Idea and creating some
Feedbacks from a Prototype.
Detailed Steps
1. Open the Prototype form called Information.
a. In the NPD and Feedback solution (this should still be open from the previous task) expand the Prototype
entity.
b. Click Forms.
c. Double-click the Information form with a Form Type of Main.
2. Add the Originating Idea, Master Prototype, Total Cost, and Total Feedback fields to the General Section.
a. In the Field Explorer pane, change the Filter to Custom Fields.
b. Select Originating Idea, and drag it below the Owner field.
c. Select Master Prototype, and drag it below the Originating Idea field.
d. Select the Total Feedbacks field, and drag it below the Master Prototype field.
e. Select the Total Cost field, and drag it below the Total Feedback Fields.
f. In the Field Explorer pane, change the Filter back to All Fields.
3. Add a new field called Planned Completion to the Prototype entity.

a. In the Field Explorer pane, click the New Field button at the bottom.
b. In the New for Prototype form in Display Name, enter Planned Completion.
c. In the Data Type list, select Date and Time.
d. In the Format list, select Date Only (this is the default value).
e. On the toolbar, click the Save and Close button.
4. Create a new one column section called Planning.

a. On the ribbon, click the Insert tab, then click the arrow below Section, then Select One Column.
b. Double-click the new section on the form.
c. In the Section Properties dialog box, in the Name and Label fields, enter Planning.
d. Select the two checkboxes Show the label of this section on the form and Show a line at the top of the
section.
e. Click OK.
5. Add the Planned Completion, Currency and Budget fields to the form.
a. In the Field Explorer, select the Planned Completion field and drag it into the Planning section. Note: if the
Planned Completion field is now showing in the Field Explorer list, you may need to Save and close the form
and reopen it.
b. Drag the Currency field below the Planned Completion field
c. Drag the Budget field below the Currency field.
6. Configure the Originating Idea field to be read-only.

a. Double-click the Originating Idea field.
b. In the Field Properties dialog box, check the box next to Field is read-only.
c. Click OK.
7. Add the Owner field to the form header.

a. On the ribbon, click the Home tab.
b. In the Select group, click the Header button.
c. In the Field Explorer, select the Owner field and drag it to the leftmost position in the Header.
d. In the Select group, click the Body button.
e. Select the Owner field located just below the Name field
f. Press Delete (Note: you are not able to delete the Owner field until you place in the Header as it is a
Required field and must be present on the form)
8. Add the Modified By and Modified On fields to the form footer.

a. Scroll down to the bottom of the form and double-click the Footer area.
b. In the Field Explorer, click the Modified By field and drag it to the leftmost position in the footer.
c. In the Field Explorer, click the Modified On field and drag it to the middle position in the Footer.
d. On the ribbon, click Save, and then click Publish.
e. Click Save and Close.
f. To ensure that all the customizations you have made to this point are available, click the Publish all
Customizations button.
g. Leave the Solution window open for later labs.
9. Test your changes to both entities by creating a Prototype from an existing Idea.
a. Switch back to your CRM Trial Organization.
b. Press F5 to refresh your browser and verify that all of your customizations are loaded into the application.
c. Click the Main button and Navigate to Sales > Ideas.
d. On the Active Ideas screen, click the New button
e. In the Name field, enter New Helmet for Kids.
f. In the Detailed Description field enter, This new helmet will be lighter and stronger.
g. In the Target Market field, enter 100
h. Save the Idea. (Notice the Prototypes Sub-Grid is now Active.)
i. Click on the New button to add a New Prototype
j. In the Name field, enter Child-125A
k. In the Planned Completion field, select a date in the future
l. In the Budget field, enter 10,000. (Notice the Key to indicate Field Security on this field).
m. Click Save
n. In the Activities Pane, click Activities.
o. Click the Add More Activities Button (…)
p. Select Feedback
q. In the Subject field, Enter Buckle Sticks
r. In the Cost field, Enter $200.00
s. Click Save and Close
t. Back on the Prototype, hover over the Total Feedbacks Rollup field and click the Refresh button. (It should
now display 1)
u. Do the same thing for the Total Cost field. (Should now display 200).
10. Test the Prototype Hierarchy

a. On the Navigation Bar, click the Main button, and select Sales > Ideas
b. Open the New Helmet for Kids Idea
c. In the Prototypes Sub-Grid, click the New Button
d. Enter Child 125B in the Name field
e. In the Master Prototype field, click the Lookup icon and Select Child 125A
f. Click Save and Close.
g. On the Navigation Bar, click the Main button, and select Marketing > Prototypes.
h. Notice that Child 125A and 125B both have a Hierarchy Icon next to their names.
i. Click the Hierarchy Icon to view the Hierarchy.
Practice 6.2: Create a Role-Based Form

Scenario
Ben Burton, Marketing Manager at Adventure Works Cycles has asked for some changes to be made to the Competitor
form to support the new product development (NPD) process. Users managing NPD need to see information about
related Ideas on Competitor records, but this is not useful to everyone. You have decided to create a second form for
the NPD users to meet their requirements without affecting other departments .
Lab Setup
Before doing this lab you need to have completed the all of the Previous Labs to this Point including Module 3
“Customizing Entities and Fields”, Module 4 “Additional Field Customizations”, and Module 5 “Relationships”.
Exercise Scenario
In this exercise you will create and test a new NPD version of the Competitor form.
Task 1: Create a Role-Based Form
High Level Steps

1. Open the NPD and Feedback solution.
2. Create a copy of the existing Information form for the Competitor entity.
3. Add a sub-grid showing Ideas on the new NPD form.
4. Assign the new form to the SalesPerson Security Role.
5. Set the form order.
Detailed Steps
1. Open the NPD and Feedback solution.

a. If Necessary switch to the NPD and Feedback by clicking the Main button and then navigate to Settings >
Solutions and double-click the NPD and Feedback solution to open it.
b. In the solution explorer expand Entities.
2. Add the Competitor entity to your Solution

a. If the Competitor entity does not exist in your NPD and Feedback Solution, in solution explorer navigate to
Entities.
b. Click the Add Existing button.
c. Locate and select the Competitor entity.
d. Click Add All Assets to include everything in your solution.
e. If you are prompted to add missing components, select No, do not include and click OK
i. If you already had the Competitor entity but are missing items, click the Add Subcomponents, and
Select all the Forms, Fields, and Relationships.
3. Create a copy of the existing Information form for the Competitor entity.
a. Expand the Competitor entity.
b. Click Forms.
c. Double-click the Competitor form that has a Form Type of Main.
d. On the ribbon, click Save As.
e. In the Save As dialog box, change the Name to read NPD.
f. In the Save As dialog box, change Description to “A form for the NPD team.”
g. Click OK and wait for the form to save and reload.
4. Add a sub-grid showing Ideas on the new NPD form.

a. In the NPD form designer, on the ribbon, click the Insert tab.
b. In the 1 Tab group, click One Column.
c. With the tab still selected, on the Home ribbon in the Edit group, click Change Properties (or you can
double-click the tab).
d. In the Tab Properties dialog box, in Name and Label enter Ideas.
e. Click OK.
f. On the Insert ribbon, in the Control group, click Sub-grid.
g. In the Set Properties dialog box, in Name, enter Ideas.
h. In the Entity list, select Ideas. Note the label is filled in based on this selection, but you can choose to
overwrite it.
i. Click Set.
j. On the ribbon click the Home tab.
k. Click Save.
l. Click Publish.
m. Click Save and Close.
5. Assign the new form to the Salesperson Security Role.

a. Click to select the NPD form.
b. On the action bar above the list of forms, click Enable Security Roles.
c. Select the Salesperson role.
d. Click OK.
6. Set the form order.

a. On the toolbar, click Form Order, then click Main Form Set.
b. Move the NPD form to the top of the list by selecting the form and clicking the up arrow above the list.
c. Click OK.
7. Test your work by opening a Competitor.

a. Click the Main button in the CRM Navigation Bar and navigate to Sales, and Competitors.
b. On the All Competitors list, click the New button.
c. Just above New Competitor, you will see the word COMPETITOR with an arrow next to it.
d. Click the Arrow and switch to the NPD from.
i. Since you are logged in as a System Administrator, you will see all forms and can switch between them.
Users who have access to both forms will see the same thing. Users with only access to a specific from
will only see the form they have access towith no option to switch.
Practice 6.3: Create and Configure an Access Team Template

Task 1: Create and Configure an Access Team Template
High Level Steps

1. Enable Access Teams for the Prototype entity.
2. Create an Access Team Template named Project Team for the Prototype entity.
3. Add a sub-grid to the Prototype Information form for Project Team members.
4. Grant Ben Burton Access to a Prototype by using the new Sub-Grid.
Detailed Steps
1. Enable Access Teams for the Prototype entity.
a. If Necessary navigate to the NPD and Feedback Solution by clicking the Main button, selecting Settings >
c. Click Prototype.
d. In the Prototype properties, in the Communication & Collaboration section, select the check box to enable
Access Teams.
e. On the toolbar, click Save, and then click Publish.
f. Leave the Solution window open for use later in this lab.
2. Create an Access Team Template named Project Team for the Prototype entity.
a. Switch back to your CRM organization, click the Main button and, navigate to Settings > Security.
b. Click Access Team Templates at the lower left.
c. On the toolbar, click New.
d. In Name, enter Project Team.
e. In Entity, select Prototype.
f. In Access Rights, select the check boxes for Read and Write.
g. On the ribbon, click Save and Close.
3. Add a sub-grid to the Prototype Information form for Project Team members.
a. Switch to the NPD and Feedback Solution.
b. In the solution explorer, expand the Prototype entity.
c. Click Forms.
d. Double-click the Information form that has a Form Type of Main.
e. In the form editor, select the Planning section.
f. On the Insert ribbon, click Section, and then click One Column to insert a new section.
g. In the Insert ribbon, in the Control group, click Sub-Grid.
h. In the Set Properties dialog box, in Name, enter ProjectTeam (no spaces).
i. In Label, enter Project Team.
j. Select the check box Display label on the Form.
k. In the Data Source section, in Records, select All Record Types. Note: the users who are added to the Access
Team do not have a direct relationship with the record, so Only Related Records will not work.
l. In Entity, select Users.
m. In Default View, select Associated Record Team Members. The Team Template property is now displayed.
n. In Team Template, select Project Team (the name of the Access Team Template you created).
o. In the lower right, click Set.
p. On the Home ribbon, click Save, and then click Publish.
q. Click Save and Close.
4. Grant a user access to the record using the new Sub-Grid.

a. Switch back to your CRM Organization.
b. Click the Main Button and navigate to Marketing > Prototypes.
c. Open the Child 125a Prototype record (Or any prototype record.)
d. Notice the Project Team Sub-Grid.
e. Click the New button.
f. Click the lookup Icon.
g. Select Ben Burton (or any user in your deployment).
h. Ben will now have Read and Write Privileges to the Record.
i. You could sign in as Ben and test access if so desired.
Module 7: Business Rules
Practice 7.1: Create a Business Rule
Scenario
After a Prototype record is created, users must not be able to move it to a different idea than the one it originated from, to make
sure that the reported outcomes of Ideas are accurate. To achieve this requirement, you configured the Originating Idea field on the
Prototype form to be read-only. This works if a user creates the Prototype record from an Idea because it inherits the Idea lookup
value through field mapping. However, when a Prototype is created from anywhere else, the record cannot be saved because the
field is required and read-only (locked).
Ben Burton, the Marketing Manager, has asked you to create a Business Rule so that users can create a Prototype and link it to an
Idea, or the other way round. You must configure a Business Rule that will test if the Originating Idea field does not contain data, and
unlock it when this condition is true.
Lab Setup
Before you perform this lab, you must complete the Add Fields to Forms lab in the Customizing Forms module, and added the
Originating Idea lookup to the Prototype form as described in that lab.
High Level Steps

1. Create a Business Rule for the Prototype entity in the NPD and Feedback Solution.
2. Configure the Business Rule as described in the lab scenario.
3. Test the Business Rule by creating a Prototype record.
Detailed Steps
1. Create a Business Rule for the Prototype entity in the NPD and Feedback Solution.
a. Switch to the NPD and Feedback Solution.
c. Expand Prototype.
d. Click Business Rules.
e. On the menu bar, click New.
2. Configure the Business Rule as described in the lab scenario.

a. Enter Originating Idea unlocked when empty as the rule name.
b. In the upper right side corner, verify that the Scope is set to All Forms.
c. Select the Condition in the editor, in properties enter unlock when Empty.
d. Under the rule set the Source to Entity
e. In Field, select Originating Idea.
f. In the Operator list, select Does not contain data.
g. Click the Apply to save the changes to the condition.
h. Click Components
i. Drag the Lock / Unlock action after the Unlock when Empty condition.
j. Verify the Properties tab is selected, and set the Display Name to Unlock
k. In Field, select Originating Idea.
l. In Status, select Unlock.
m. Click the Apply to save the changes to the action.
n. Click Components
o. Drag the Lock / Unlock action below the Unlock when Empty condition.
p. In Properties enter, Lock Field
q. In Field, select Originating Idea.
r. In Status, select Lock.
s. Click Apply to save the changes to the action.
t. At the top left of the window, on the command bar, click Save.
u. On the command bar, click Activate,
v. In the Process Activate Confirmation dialog box, click Activate to confirm.
w. Close the Business Rule.
3. Test the Business Rule by creating a Prototype record.

a. Switch to your main CRM application.
b. Click the Main button, and navigate to Marketing > Prototypes.
c. On the command bar, click New.
d. In Name, enter New Bike Lock.
e. Notice the Originating Idea field is unlocked.
f. In the Originating Idea field, click the lookup icon and then select an existing Idea record.
i. Notice a padlock appears next to the Originating Idea field
g. Click it again and verify that it does not respond because it is now locked.
h. On the command bar, click Save.
i. Notice that the field continues to display a padlock icon since it is still locked.
Module 8: Views and Visualizations
Practice 8.1: Modify the Quick Find View

Adventure Works Cycles staff frequently use the Quick Find feature in Microsoft Dynamics 365. Some users need to search for
Contacts based on the city in which they are located. Because the City field is not configured as a find column by default you must
modify the Quick Find view by adding the Address 1: City field as a find column.
Exercise Scenario
In this exercise you must modify the Quick Find Active Contacts view to enable the Address 1: City field as a find column in order to
allow users to search for Contacts based on the city in which they are located.
Task 1: Customize the Prototype Active Prototypes View.

High Level Steps
1. Open the Active Prototypes view in the NPD and Feedback Solution.
2. Remove the Created On Column and Resize the Name Column.
3. Add the Originating Idea, Planned Completion, and Owner fields from the Prototype entity..
4. Add the Target Market field from the Idea entity.
5. Move the Planned Completion field directly after the Name field.
Detailed Steps
1. Open the Quick Find Active Contacts view in the NPD and Feedback Solution.
a. Switch to your NPD and Feedback. Otherwise click the Main button, and navigate to Settings > Solutions and double-
click the NPD and Feedback Solution to open it.
d. Click Views.
e. In the list of views, double-click Active Prototypes.
2. Remove the Created On Column and Resize the Name Column.

a. In the Column Headings click the Created On column.
b. In the Common Tasks pane at the right side of the view designer, click Remove.
c. Click the Name column.
d. In the Common Tasks pane at the right side of the view designer, click Change Properties.
e. Select 200px, and click OK.
3. Add the Originating Idea, Planned Completion, and Owner fields from the Prototype entity.
a. In the Common Tasks pane at the right side of the view designer, click Add Columns.
b. In the Add Columns dialog, select Originating Idea, Planned Completion, and the Owner fields.
c. Click OK
4. Add the Target Market field from the Idea entity.

a. In the Common Tasks pane at the right side of the view designer, click Add Columns.
b. Click the Record Type selector box, and choose Originating Idea (Idea)
c. Select the check box next Target Market Size.
d. Click OK
5. Move the Planned Completion field directly after the Name field.
a. Click to select the Planned Completion field
b. Using the arrows in the Common Tasks pane, move it after the Name column.
c. Click Save and Close.
d. In the solution explorer, click the Prototype entity node.
e. On the toolbar, click Publish.
Practice 8.2: Create a Custom View

Scenario
Adventure Works Cycles requires two custom views to be created in their Microsoft Dynamics 365 installation. The details of the
views are as follows:
A new public view for the Prototype entity is required. The view must be named All Prototypes for My Ideas. To create the view,
you must copy the Active Prototypes view, add a filter to the view, and add the Modified On and Originating Idea fields as columns.
You must also create a new view for the Feedback entity. The view should be named Service Feedback Last 3 Months and be filtered
to show feedback for resolved cases that were modified in the last three months. The view must display columns for the Satisfaction
Rating, Owner, Modified On date of the Case, and the Owner of the Case.
Lab Setup
Before you perform this lab, you must complete the Create Custom Entities lab and the Create a Custom Activity Entity lab in the
Customizing Entities module, and create the Prototype and Feedback entities as described in those labs.
Exercise Scenario
In this exercise you must create the All Prototypes for My Ideas view and the Service Feedback Last 3 Months view following the
requirements specified in the lab scenario.
Task 1: Create a Custom View for the Prototype Entity
High Level Steps

1. Open the list of Prototype views in the NPD and Feedback solution.
2. Create a copy of the Active Prototypes view and name it All Prototypes for My Ideas.
3. Update the filter criteria of the new view.
4. Add the Modified On and Originating Idea columns to the view.
5. Publish the entity and test the view.
Detailed Steps
1. Open the list of Prototype views in the NPD and Feedback solution.
a. Switch to your NPD and Feedback. Otherwise click the Main button, and navigate to Settings > Solutions and
double-click the NPD and Feedback Solution to open it.
d. Click Views.
2. Create a copy of the Active Prototypes view and name it All Prototypes for My Ideas.
a. Double-click the Active Prototypes view.
b. When the view is open, click Save As.
c. Change the Name to All Prototypes for My Ideas and then click OK.
d. Update the filter criteria of the new view.
e. In the Common Tasks pane on the right side of the view designer, click Edit Filter Criteria.
f. In the Select control, click the drop-down and select Originating Idea from the Related section in the lower part of
the list.
g. Underneath Originating Idea, in the Select control, select the Owner field.
h. Make sure that the condition list to the right of Owner contains Equals current user.
i. At the lower right corner of the Edit Filter Criteria dialog box, Click OK.
3. Remove the Owner, Target Market Size and Planned Completion Fields.
a. Select the Owner column.
b. In the Common Tasks area, click Remove, and OK to Confirm.
c. Select Target Market Size column.
d. In the Common Tasks area, click Remove, and OK to Confirm.
e. Select the Planned Completion column.
f. In the Common Tasks area, click Remove, and OK to Confirm.
4. Add the Created On and Modified On columns to the view.
a. In the Common Tasks pane, click Add Columns.
b. In the Add Columns dialog box, select the check boxes next to Created On and Modified On, and then click OK.
c. Verify Originating Idea column is to the left of the Name column.
d. Select the Originating Idea column, and then in the Common Tasks pane, click Change Properties.
e. In the Change Column Properties dialog box, select 200px and click OK.
f. Select the Modified On column.
g. Verify that Modified On is just to the right of Created On.
h. If not, In the Common Tasks area, click the right arrow until the Modified On column is to the right of the Created
On column.
j. In the solution explorer, click the Prototype entity.
k. On the toolbar, click Publish.
l. Leave the Solution window open for use in later labs.
Task 2: Create a Custom View for the Feedback Entity

High Level Steps
1. In the NPD and Feedback Solution, create a view for the Feedback entity named Service Feedback Last 3 Months.
2. Modify the filter criteria as described in the lab scenario.
3. Add columns to the view as described in the lab scenario.
4. Resize the new columns and configure sorting for the view.
5. Publish and test the view.
Detailed Steps
1. In the NPD and Feedback Solution, create a view for the Feedback entity named Service Feedback Last 3 Months.
a. If necessary, switch to the NPD and Feedback Solution.
b. In the solution explorer, expand the Entities node.
c. In the list of entities, expand Feedback.
d. Click Views.
e. On the menu bar above the list of views, click New.
f. In Name, enter Service Feedback Last 3 Months and click OK.
2. Modify the filter criteria as described in the lab scenario.
a. In the Common Tasks pane, click Edit Filter Criteria.
b. In the Edit Filter Criteria dialog box, click the Select control, and then in the Related section of the list select
Regarding (Case).
c. Underneath Regarding (Case), in the Select control, select the Status field.
d. Next to the Enter Value: Status field, click the ellipsis button.
e. Double-click Resolved in the Available Values list to add Resolved to the Selected Values list, and then click OK
f. Underneath Regarding (Case), in the Select control, select Modified On.
g. In the condition list (that currently contains On), select Last X Months.
h. In the Choose Date control, type 3.
i. At the lower right corner of the Edit Filter Criteria dialog box, Click OK.
3. Add columns to the view as described in the lab scenario.
a. In the Common Tasks pane, click Add Columns.
b. In the Add Columns dialog box, select the check boxes next to Date Created and Satisfaction Rating, and then click
OK.
c. In the Common Tasks pane, click Add Columns.
d. In the Add Columns dialog box, in the Record Type list, select Regarding (Case).
e. Select the check boxes next to Modified On and Owner, and then click OK.
4. Resize the new columns and configure sorting for the view.
a. Double-click the Owner (Regarding) column.
b. In the Change Column Properties dialog box, select 125px, and then click OK.
c. In the Common Tasks pane, click Configure Sorting.
d. In the Configure Sort Order dialog box, in the Sort By list, select Date Created.
e. Underneath Date Created, select Descending Order so that the newest records will be displayed at the top.
f. Click OK.
g. On the toolbar, click Save and Close.
5. Publish and test the Views.
a. In the solution, click the Publish All Customizations button.
b. Leave the Solution window open for use in later labs.
c. Switch back to your main CRM application.
d. Click the Main button and navigate to Service > Activities.
e. Click the view selector (this shows My Activities because this is the label of the current view).
f. In the view selection list, click Feedback, then in the submenu select Service Feedback Last 3 Months. The new
view will be displayed, showing test records created in earlier labs.
g. Click the Main button and navigate to Marketing > Prototypes
h. Using the view selector Select the All Prototypes for My Ideas this will show all prototypes for any Ideas that you
are the Owner of.
Practice 8.3 Create a Custom Chart
Scenario
Judith Walker, Head of Services at Adventure Works Cycles, needs to assess customer satisfaction for recently resolved service
Cases.
She asks you to create a chart to use on a dashboard showing the number of Feedback responses in each month, broken down by
the satisfaction rating. Judith already has a dashboard which shows volumes of work in the service department. For this new chart,
she needs to see how the proportions of the satisfaction ratings change from month to month rather than the actual number of
responses.
Objectives
In this lab you will create a chart of Feedback records, using a category from the Cases they are related to. You will then test the
chart before adding it to a dashboard.
Lab Setup
Before starting this lab, you will need to complete the lab exercise “Create a Custom View for the Prototype Entity” in the module
“Customizing Views”.
Exercise Scenario
To meet Judith’s requirements you must create a chart categorized by the month the related Case was resolved.
Instead of creating a custom field to use for the date a Case is resolved, note that you can use the Modified On field which will
provide the same result. Cases cannot be modified after they are closed (unless they are re-opened first). When you use the chart on
a dashboard you will be able to associate it with a view of recently resolved Cases to make sure this is a valid approach.
Because Judith is more interested in the relative proportions of the satisfaction ratings each month than in the actual number of
Cases closed or Feedback responses received, you must create a 100% Stacked Column to make the visualization clearer.
Task 1: Create a 100% Stacked Column Chart

High Level Steps
1. Open the NPD and Feedback Solution and create a chart for the Feedback entity.
2. Configure the new chart as described in the exercise scenario.
3. Save and publish the new chart.
4. Create some Feedback records.
5. Test the new chart.
Detailed Steps
1. Open the NPD and Feedback Solution and create a chart for the Feedback entity.
a. Switch or Navigate back to your NPD and Feedback solution. Or click the Main button and navigate to Settings >
b. Expand the Entities node of the solution explorer.
c. Expand the Feedback node, then click Charts.
d. In the action bar, click New. The chart configuration form will open
2. Configure the new chart as described in the exercise scenario.
a. In the View used for chart preview at the top of the form, select the view called Service Feedback Last 3 Months.
b. Below the heading Legend Entries (Series) click Select Field and select the Satisfaction Rating field from the top
section of the list.
c. To the right of the field name, click Count:All and select Count:Non-empty.
d. To the right of the series row, click the Column button, then in the gallery which appears click the Column button
(on the left), then select 100% Stacked Column.
e. Below the heading Horizontal (Category) Axis Labels click Select Field and select the Modified On (Regarding)
field. Leave the date grouping at Month.
f. Click Add a Category, then Select Field and select the Satisfaction Rating field from the top section of the list.
g. Enter a new chart name Feedback by Case Closed Month and Satisfaction (or another name if you prefer).
3. Save and publish the new chart.
a. Click Save and Close to close the chart configuration form.
b. Click the Feedback entity in the solution explorer.
c. On the toolbar, click Publish.
4. Create some Feedback records.
a. Leave the NPD and Feedback window open for later labs.
b. Switch back to your main CRM application and click the Main button, and Navigate to Service > Cases.
c. On the command bar, click New Case.
d. Click the Case Title field.
e. Enter Test1 (or your own name for this test record).
f. Point to or click the Customer field, then click the lookup button to the right of it and select any Account from the
list.
g. The record will be automatically saved.
h. In the social pane, under the Activities tab, click Add More Activities (with an ellipsis icon …), then click Feedback.
i. In the new Feedback form, click the Satisfaction Rating field and use the option set control to select a rating.
j. On the command bar click Save then click Mark Complete.
k. Click the Regarding field to return to the Case form.
l. Repeat steps H. through K. several times, selecting different satisfaction ratings for each new Feedback record.
m. With the Case form open, on the command bar click Resolve Case.
n. In the Resolve Case dialog box, click the Resolution field and enter Fixed.
5. Test the new chart.
a. Navigate to Service > Activities.
b. Click My Activities to show the list of available views.
c. Click Feedback, then in the sub-menu, click Service Feedback Last 3 Months.
d. On the right hand side of the screen, click Charts to expand the chart pane.
e. Note that the column of the chart extends to 100 (%).
f. Point to any data point in the chart (one column segment) and check that the infotip shows the correct number of
responses.
g. Click a data point and confirm the Service Feedback Last 3 Months view is filtered to match the category for that
data point.
Practice 8.4: Create a Modified Dashboard

Walker, Head of Services wants to include the chart of feedback ratings for recent service cases on a dashboard where it will be
easily visible to all members of the service department. The department does not use Goals in Microsoft Dynamics 365, so Judith has
identified that the Goal Progress chart on the Customer Service Performance dashboard can be removed to make space for the new
one.
Exercise Scenario
In this exercise you create a copy of the Customer Service Dashboard, remove the Goal Progress chart and add the Feedback
Satisfaction chart you created in the first lab in this module. You will then move the new chart to the top left to give it more
prominence and then test your changes.
Task 1: Copy and Modify the Customer Service Performance Dashboard

High Level Steps
1. Create a copy of the Customer Service Performance dashboard in the NPD and Feedback solution.
2. Remove the Sales Pipeline Chart and replace it with the Feedback chart you created in the previous exercise.
3. Publish and test your new dashboard.
Detailed Steps
1. Create a copy of the Customer Service Performance dashboard in the NPD and Feedback solution.
a. Switch to the NPD and Feedback solution if you still have the window open, otherwise Click the Main button, and
navigate to Settings > Solutions and double-click the NPD and Feedback solution to open it.
b. In the solution explorer, click Dashboards.
c. On the action bar, click Add Existing.
d. Select Dashboard.
e. In the Select solution components dialog box, select Sales Dashboard click OK.
f. Verify the Sales Dashboard is selected, and on the action bar, click Save As.
g. In the Dashboard Properties dialog box, enter Customer Service and Feedback as the Name of the Dashboard.
Enter something suitable for the Description (note you cannot change this later).
h. Click Enable for Mobile.
i. Click Save.
2. Remove the Sales Pipeline Chart and replace it with the Feedback chart you created in the previous exercise.
a. Double-Click the Customer Service and Feedback Dashboard to open it up
b. Locate the Sales Pipeline chart (Bottom Row, Middle Column)
c. Click to Select it
d. Press Delete.
e. On the Command Bar at the top, click the Chart button
f. Select Feedback from the Record type dropdown.
g. Select Service Feedback Last 3 Months for the view.
h. Select Feedback by Case Closed Month and Satisfaction under Chart.
i. Click Add.
j. Click the select the Feedback by Case Closed Month and Satisfaction chart
k. Drag it between the Accounts list and the Top Customer chart
l. Click Save.
m. Click Close
n. Click to select the Customer Service and Feedback Dashboard, and click the Publish button
3. Test the Dashboard
a. Switch back to you CRM organization.
b. Click the Home button (Microsoft Dynamics CRM)
c. In the dashboard window, click the arrow next to Sales Activity Dashboard
d. Choose Customer Service and Feedback.
Practice 8.5: Create and Apply a Dynamics 365 Theme

Adventure Works Cycles, would like to modify the colors in their Dynamics 365 environment to reflect their company colors which
primarily Red and Gray. They are only concerned with the Navigation elements at the top of the screen.
Exercise Scenario
In this exercise you copy the existing Default Dynamics 365 theme and modify it to fit based on Adventure Works Color Pallet.
The want to use the Following:

 Set the Navigation Bar color to a Red using the color code #e34444
 Set the Navigation Bar Shelf color to a very Light gray using the color code #e2e2e2
 Set the Heading used in the Navigation bar to a Dark gray using the color code #6e6e6e
Task 1: Custom Dynamics 365’s Theme

High Level Steps
4. Create a Clone of the existing default Theme, called ADV Works Theme
5. Change the Navigation Bar Color, Navigation Bar Shelf Color, and Header Color to the colors outlines above.
6. Publish the Theme.
Detailed Steps
4. Create a Clone of the existing default Theme, called ADV Works Theme
a. In your main application click the Main button and navigate to Settings > Customizations.
b. Select Themes.
c. Select the Default Theme.
d. Click Clone.
5. Change the Navigation Bar Color, Navigation Bar Shelf Color, and Header Color to the colors outlines above.
a. Double-click the Copy of Default Theme to open it.
b. In the Theme Name, enter ADV Works Theme.
c. In the Navigation Bar Color field, enter #34444 (Preview will change to red)
d. In the Navigation Bar Shelf Color, enter #e2e2e2 (Preview will change slightly)
e. In the Heading Color, enter #6e6e6e (Preview will change to a Dark Gray)
f. Click Publish Theme.
Module 9: Customizing for Interactive Service Hub
Practice 9.1: Modify the Quick Find View

Adventure Work’s help desk often need to send out replacement parts to customer when something fails. Once a technician
determines that a replacement part needs to be sent out to the customer they need to ship out a package to the customer that
contains the necessary parts. The technician will need to note the following information about the package:
 The reason for the replacement

 Who the package is going to.
o Customer Name, Shipping Information, and specific contact that is should be sent to the attention of.
 The Case that that the need for the replacement part originated from.
Adventure Works uses several different package delivery providers depending on the on how fast the product needs to arrive to the
customer. Below is the general rule that is used to determine which provider to use:
 Next Business Day: FedEx

 2nd Day: UPS
 3 to 5 Days: FedEx
 Over 5 Business Days: USPS
Once the Package is created and sent to the customer, the representative will also need to be able to determine the following:
 The date the Package was Shipped

 The Tracking Number provided by the Company
 The estimated delivery Date, so the tech can verify they received it
 The actual date the package was delivered
 Any specific details around the delivery, such as where it was dropped off, who signed for it, etc.
 Are they required to return the original parts
o If so:
 When were they sent back
 When did they arrive
 Did we get everything
The Technician is not allowed to resolve the case until the following has been completed.
 The replacement Parts have been installed and the problem is solved
The original parts have been sent back and received by Adventure Works.
Exercise Scenario
In this exercise you be customizing the Interactive Service Hub interface to enable the Requirement Listed above.
Step-by-Step: Setup Supporting Customizations

Below are step by step instructions that will guide you through the solution. Compare it to what you did to see how closely your
solution reflected the one below.
Practice 9.1: Create Replacement Package Entity

.
1. In your Dynamics 365 online organization, navigate to Settings > Customization > Solutions
2. Click New to create a new solution.
3. Name the Solution Replacement Parts, and enter a version number of 1.0.0.0
4. In the Publisher filed, click the Lookup Icon, Select Look Up More Records, and click the New button.
5. Enter ISH in both the Display Name and Prefix Name fields
6. Click Save and Close.
7. Select ISH and click Add.
8. Click Save to save the solution and leave it open.
9. Click on Entities, select Add Existing, Choose Case, and click OK.
10. In the Select Entity Assets dialog, click Add All Assets and click Finish.
a. If you and prompted to add the Mobile CSR security Role, click Yes, include required Components and click OK.
11. Click New to create a new entity and enter information as noted below:
a. Display Name: Replacement Package.
b. Plural Name: Replacement Packages.
c. Display in the Service Area.
d. Check Enable for interactive service.
e. Check Enable Process flows.
12. Click Save and Close to Create the Entity.
13. Under Entities, expand the Replacement Package entity, click fields.
14. Add the following fields to the entity:
Field Name Data Type Global Filter Sortable
Description Multiple Line of Text NA No
Ship Date Date and Time Yes Yes
Tracking Number Single Line of Text NA No
Est. Delivery Date Date and Time Yes Yes
Act. Delivery Date Date and Time Yes Yes
Delivery Details Multiple Line of Text NA No
Return Original Parts Two Options (Yes/No) Yes No
Number Required Whole Number No No
Number Returned Whole Number No No
All parts Returned Two Option (Yes/No) Yes No
15. Add a new Option Set called Shipping Method with the Following Values
a. FedEx (Set Color to #000066)
b. UPS (Set Color to #330000)
c. USPS (Set color to #990000)
d. None (Set color to #000000) Set this as Default
16. Set the Field to Appear in the Global Filter, and Be Sortable in the Interactive Experience
18. You will also need to add the following Lookup fields to the Entity:
Name Lookup Entity
Associated Case Case
Customer Account
Point of Contact Contact
Next you will create Several Calculated Fields to populate the Shipping Information based on the Account Selected.
19. If necessary click New, Enter Street 1 in the Display Name, Select Calculated for Field Type, and click Edit.
20. Click Add Action, enter ish_customer.address1_line1, Click the Check Mark ,
22. Click Save and New and repeat to create the following calculated fields:
Name Formula
City ish_customer.address1_city
State ish_customer.address1_stateorprovince
Postal Code ish_customer.address1_postalcode
Phone ish_customer.telephone1
23. Under the Replacement Package entity, click on the N:1 Relationships, and double-click the relationship where Case is the
Primary Entity.
24. Select Mappings and click New.
25. From the Source Entity Fields, click to select customer ID and from the Target Entity Fields select ish_customer in the
Target.
26. Click OK.
27. Click New Again
a. Select primarycontactid in Source Entity Fields and ish_pointofcontact in the Target Entity Fields.
b. Click OK.
28. Click Save and Close
Practice 9.2: Customize the Replacement Package’s views and Interactive form.
Now that we have all of the necessary fields, relationships, and mappings defined, we are going to customize the views and forms
that will be used for the Replacement Package entity in ISH.
1. If necessary, in your Dynamics 365 online organization, navigate to Settings > Customization > Solutions
2. Open the Replacement Parts solution.
3. Expand the Entities and Replacement Package, Views.
4. Double Click to Open the Active Replacement Packages View
5. Make the Following Changes
a. Remove the Created on Field
b. Set the Name field to 200 PX
c. Add the following Fields
i. Act Delivery Date
ii. Customer
iii. Est Delivery Date
iv. Point of Contact
v. Ship Date
vi. Tracking Number
d. Adjust the fields to display in the following order
i. Name
ii. Customer
iii. Point of Contact
iv. Ship Date
v. Est Delivery Date
vi. Tracking Number
vii. Actual Delivery Date
6. Click Save and Close to close the view.

7. Under the Replacement Package Entity, click on Forms.
8. Double-Click to open the Main interactive form.
9. In Field Explorer, filter by Custom Field
10. Add the following Fields to the General Section:
a. Associated Case
b. Customer
c. Point of Contact
d. Phone
e. Description
11. From the Insert Tab, click section and choose one column.
12. Double click the new section, change the Label to Shipping Info
13. Select show the label on the form
14. Click OK.
15. Add the following fields to the Shipping Info Section.
a. Ship Date
b. Shipping Method
c. Tracking Number
d. Est. Delivery Date
e. Act Delivery Date
f. Delivery Details
16. Move the Shipping Info Section below the Related Section
17. From the Insert Tab, click section and choose one column
18. Double click the new section, change the Label to Address Info,
19. Select show the label on the form, and click OK.
20. Add the following fields to the Address Info Section:
a. Street 1
b. City
c. State
d. Postal Code
21. If Necessary, move the Address info section below the general section
22. From the Insert Tab, click section and choose one column
23. Double click the new section, change the Label to Return Details,
24. Select show the label on the form, and click OK
25. Add the following fields to the Return Details Section:
a. Return Original Parts
b. Number Required
c. Number Returned
d. All Parts Returned
26. If Necessary Move the Return Details section below Shipping Info.
27. Save and Close the Form.
28. Publish All Customizations.
Create two Replacement Package Charts.

3. Under Replacement Package, select charts, and click New.
4. Enter Packages Shipped by Week in the Name.
5. In the Legend Entries select Name and choose Count All.
6. In the Horizontal Axis, select Ship Date and Choose Week.
8. Click New, and Enter Packages by Provider for the Name.
9. In the Legend, Select Name, and Choose Count All.
10. In the Horizontal Axis, Select Shipping Method.
Practice 9.2: Customizing Interactive Service Hub
3. Under Replacement Package, select dashboards, and click new > Interactive experience dashboard.
4. Select 2-Column Overview Dashboard and click Create.
5. Enter Replacement Packages in the Name Field.
6. Under the Visual Filters Section click one of the Add Chart icons, and select the Packages by provider chart.
7. Click Add.
8. Click the other Add Chart Icon, Select the Packages Shipped by Week
9. Click Add.
10. Under the Streams Section, click the Add Stream Icon, Select Active Replacement Packages for the View
11. Click OK.
12. Click the Save button then Close the dashboard
Customize the Case Interactive from to include Replacement Packages.

3. Expand the Case Entity, click forms, and double-click to open the Case for Interactive experience form.
4. Double click the related section to open the properties, un-check the lock section on form check box.
5. Click OK.
6. On the Form the insert tab, click Sub-grid, and Name it Replacement_Packages
7. Click the Lookup button on the Tab Icon field, and select msdyn_/Images/actionsArrow.png
8. In the Data Source Change the Entity field, to Replacement Packages (Associated Case)
9. The Properties for the Sub-Grid should match the below image:
10. Click Set
11. Save and Close the Case Form.
Customize Existing ISH dashboards to contain the Replacement Packages Entity.
1. If necessary, in your CRM online organization, navigate to Settings | Customization | Solutions

3. Select Dashboards, Click Add Existing | Interactive Experience Dashboard.
4. Select the Tier 1 and Tier 2 dashboards
5. Click OK.
6. Open the Tier 1 Dashboard, click in the Streams section at the bottom to add a new stream.
7. Select Display an Entity View, Select the Replacement Package Entity, and use the Active Replacement Packages View.
8. Click OK.
9. Save and Close the Dashboard.
10. Open the Tier 2 Dashboard, locate the open Tile section in the bottom right, and click to Add a new Tile.
11. Select Display an Entity View, Select the Replacement Package Entity, and use the Active Replacement Packages View.
12. Click OK.
13. Save and Close the Dashboard.

Practice Labs

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Practice Labs

Uploaded by

Copyright:

Available Formats

81059 Customizing Dynamics 365 for Sales and Service

Before you begin

Obtaining a Dynamics 365 Trial

7. Once everything completes, click the You’re ready to go… link

High Level Steps

3. Add Account, Contact and Campaign entities to the Solution.

5. Add the Salesperson Security Roles to the Solution.

High Level Steps

3. Configure the Salesperson Security Role as described in the exercise scenario.

Task 1: Create the Feedback Entity

2. Test the Feedback Custom Activity.

Practice 3.3: Create Custom Fields

Field Name Data Type Additional requirements

High Level Steps

2. Add the Detailed Description field according to the scenario.

3. Add the Target Market Size field according to the scenario.

The field should be configured as follows:

Field Name Requirements

You are required to perform the following tasks:

Task 1: Create a Global Option Set Called Ratings

High Level Steps

2. Add a new Option Set Field to the Feedback entity.

Practice 4.2: Create a Calculated and Rollup fields

High Level Steps

4. Add a Cost field for the Feedback Entity

5. Add a Budget field on the Prototype Entity

6. Create a Total Cost Rollup field on the Prototype entity

Practice 4.3: Configure Field Security

High Level Steps

Create a 1:N Relationship

Create a N:N Relationship

High Level Steps

2. Link an Idea to an existing Competitor.

Practice 5.3: Customize Relationship Mappings

1. Open the 1:N relationship between Idea and Prototype

2. Create a mapping between the Owner fields of both entities.

3. Test the field mapping by creating a Prototype from an Idea.

Practice 5.4: Create a Hierarchical Relationship

High Level Steps

2. Define the Hierarchy Setting for the Prototype Entity.

2. Define the Hierarchy Setting for the Prototype Entity.

Field Name Properties

High Level Steps

4. Add a Sub-Grid to the Idea Entity to show related Prototypes.

Task 2: Customize the Prototype Form and Add New Fields

High Level Steps

3. Add a new field called Planned Completion to the Prototype entity.

4. Create a new one column section called Planning.

6. Configure the Originating Idea field to be read-only.

7. Add the Owner field to the form header.

8. Add the Modified By and Modified On fields to the form footer.

10. Test the Prototype Hierarchy

Practice 6.2: Create a Role-Based Form

Task 1: Create a Role-Based Form

High Level Steps

1. Open the NPD and Feedback solution.

2. Add the Competitor entity to your Solution

4. Add a sub-grid showing Ideas on the new NPD form.

5. Assign the new form to the Salesperson Security Role.

6. Set the form order.

7. Test your work by opening a Competitor.

Practice 6.3: Create and Configure an Access Team Template