Module 01 - Introduction to MSDynCRM2013 Flashcards

1
Q

Give two examples of other methods you may have to use to accomplish customization that you cannot do with just “point and click”.

A

JavaScript to manage client side behaviour of forms, and creating .Net plugins for creating complex tasks.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Customization is used interchangeable with what term in this course?

A

Configuration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

“Point and click” customization is distinct from…?

A

Extending or development, which requires external software tools to create new components such as .net plugins or JavaScript functions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is a Microsoft Dynamics CRM solution?

A

Solutions let you package a set of custom components that work with one another to provide functionality that some or all users must have.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Why use Solutions?

A

A Solution is a way to organize customization that you make to the system to meet a specific set of business requirements. You can deliver a whole set of changes at the same time.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

How does a Solution help you keep focus?

A

You can work on the components you must have without confusion from everything else in the system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

How does a Solution help you record changes?

A

You can detail each Solution separately and relate each Solution to the original requirements, instead of one large document.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

How does a Solution make it easier to deliver?

A

When ready, it can be exported with necessary components packaged together for testing, or in production. Will only contain what you need, and is thus more manageable.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What else can you do with an exported solution package?

A

You can save it, to keep it as a part of your change control records.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Why would you want to save an exported Solution?

A

To help roll back certain unwanted changes in some circumstances.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What happens when an Organization is created in Microsoft Dynamics CRM?

A

The system creates a Solution named the Default Solution that contains all the components in the system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Are you able to modify to components of the system directly in Default Solution?

A

Yes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Where else can you export the Default Solution?

A

It can be exported from the application and imported into another Microsoft Dynamics CRM Organization.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What can’t you export the Default Solution as?

A

You cannot export it as a Managed Solution. You cannot deploy a complete Default Solution from CRM on-premises to CRM Online or the other way around.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What can you deploy between two Microsoft Dynamics CRM 2013 systems that use either platform?

A

Custom Solutions can be deployed between either platform.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

It is recommended that for each separate set of business requirements you are trying to meet, you should…?

A

Create a new Solution for each separate set instead of customizing the Default Solution directly.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

How do you create a new Solution?

A
  1. Sign in with a System Customizer or System Admin Security Role > 2. Settings > 3. Solutions > 4. You will see list > 5. New > 6. Complete fields in New Solutions form and save
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What is the Display Name on the New Solution Form?

A

What you will refer to the new Solution as.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Explain the meaning of the numbers separated by decimal points in the Version field.

A

It follows the form; major.minor.build.revision – you can change it to suit your change management process and can choose year.month.day.revision

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

The Solution description field can hold how many characters before truncating?

A

2000 characters.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What is a best practice of the Solution description?

A

Should contain a summary of the functionality that the Solution provides. And short “change control” details, as well as adding information about new items or modifications that are made.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Where is the description included when you export your Solution?

A

In the XML of your solution package when you export.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

What is the Publisher for the Solution in the New Solution form used for?

A

It shows the other customizers of your system who created the Solution and the customizations the Solution includes, and specifies a prefix for many new components you create.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Why is the prefix important when creating entities, fields or relationships in any Solution?

A

On creation of any entity, field or relationship in a Solution linked to a particular Publisher, the prefix you define is added before the schema name used internally in the system for that component. Ensures that the components remain unique even if two Publishers name the components the same.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

What is the minimum and maximum character requirement for the Prefix?

A

Minimum of 2 characters, maximum of eight lowercase letters and numbers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

How should you define the prefix?

A

The prefix should describe who is doing the changes and on behalf of whom.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

Why is the publisher especially important when exporting a solution?

A

Because only Solutions with the same publisher will be able to update those components.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

How do you create a new Publisher for your Solution?

A
  1. Lookup in Publisher >2. If Publisher doesn’t currently exist >3. Lookup more Records and create new >4. Enter a display name>5.Add Description >6.Add a Prefix >8.Enter Contact Details >9.Save and Close >10. Add Publisher to solution
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

What happens when you tab or click away from the Prefix field?

A

Option Value Prefix is automatically generated.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

What happens to the Display name when you navigate away?

A

The form will copy the Display Name to the Name field and remove and characters that are not letters or numbers, includes removing spaces. (Removes nonalphanumeric characters and spaces).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

What is the Option Value Prefix?

A

When modifying an Option Set to add new items, the Option Value Prefix number provides the default integer values for these items to avoid conflicts between different customizers. Can be overridden.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

What is recommended if you have more than one customizer working on different sets of requirements?

A

That you create one or more new Publishers and use these for solutions being created to separate customizations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

Should you have a different Publisher for every Solution?

A

No, only for solutions being modified by different people or for different purposes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

A Solution is a container for…

A

A set of components that work together to provide the functionality for which you are asked.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

To modify components in a Solution…

A

You can create new ones or add existing components from the system into your solution.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

What happens to the Default Solution even if you’re working on your own Solution?

A

Any components modified or created are changed in the Default Solution because your Solution contains references to these components, not copies.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

If you delete the Solution you are customizing, what happens?

A

You remove the “wrapper” around the components. Component cores remain unchanged in the system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
38
Q

What happens if two customizers work on the same item in two separate Solutions on the same system?

A

Each customizer will be able to view the other’s changes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
39
Q

What is an advantage of the fact that multiple sets of changes can be present in a solution package that customizers export?

A

Interaction between the changes can be viewed and tested.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
40
Q

What is a disadvantage of the fact that multiple sets of changes can be present in a solution package that customizers export?

A

If one set of changes is incomplete and another set is deployed to another system. Will need process to handle such situation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
41
Q

What state does a newly created/freshly modified Solution remain in?

A

An unmanaged state.

42
Q

When does an unmanaged Solution become a managed Solution?

A

When it is exported and then imported into a target system.

43
Q

What happens if you delete a Managed Solution?

A

It will delete all the components that a Solution includes, and any related data from custom entities in the Solution.

44
Q

If changes are needed, when should you use an existing Solution and update the version?

A

When changes are minor, like changes that are a result in response to feedback received from user acceptance testing before deploying to production.

45
Q

When should you create a whole new Solution?

A

When you receive a completely different set of requirements. And original Solution has many components that no longer need updates.

46
Q

What is the problem with the approach where customizers work on separate systems and deploy to a single test system, then to live environment?

A

You may not see conflicts in the functionality until Solutions are brought together. And there may be duplication of effort.

47
Q

How to add new/existing components to your Solution?

A
  1. Settings > Solutions. >2. Components >3. Dropdown arrow on New to select type >4. Form opens, add existing or select node from solution explorer tree to add new/existing components of x type.
48
Q

How do you remove a component from a Solution?

A

Select it in the relevant node of solution explorer or main list. Select remove//delete.

49
Q

What does Remove do?

A

Removes the reference to your Solution. Component remains in the Default solution.

50
Q

What does Delete do?

A

It removes component from the whole system.

51
Q

Which components cannot be deleted?

A

System entities (those built into the system). A component that depends on another component.

52
Q

What cannot be added to a Solution?

A

Users, teams, business units, queues, goals, subject hierarchy and anything relating to the product catalog cannot be added to a Solution because they are data records.

53
Q

If you need to use records that cannot be added to a solution, how to best manage?

A

Matching names in all systems, and rely on record names for queries and references. Or use GUIDs for the records in your import file.

54
Q

What does the exported solution package typically consist of?

A

Solution package is a .zip file. It contains XMLs, .xaml, .dll, image files depending on components in Solution.

55
Q

How to export a Solution?

A
  1. Select a top level component node in solution explorer or on Information / Components or navigate to Settings > Solutions. >2. Click Export Solution in the ribbon.
56
Q

For internal changes being deployed from one system to another you should export your solution as ?

A

Unmanaged.

57
Q

What are managed solutions used for?

A

To distribute customizations.Should always export an unmanaged copy in case original environment fails.

58
Q

How to import a Solution?

A

Settings > Solutions > Import

59
Q

Where can you find an accurate record of what is imported?

A

In the imported solution package compressed zip file.

60
Q

You can’t uninstall an unmanaged solution, but you can …?

A

Delete it. It does not reverse the import process. Imported changes are incorporated completely into the system.

61
Q

What happens if you delete an unmanaged Solution?

A

No components are deleted, regardless of whether Solution was created within system or Solution was imported.

62
Q

What happens when several Solutions are imported?

A

The last one that is imported overwrites previous changes in the system. Order is important.

63
Q

What happens when you import a managed Solution?

A

No changes are made to system components. The Solution keeps definitions of components separately.

64
Q

What happens when you delete a managed Solution?

A

It deletes all components that are imported and leave system same as before Solution was imported.

65
Q

Which version numbers are relevant when importing?

A

The major and minor version numbers (first two) as you cannot import a Solution that is exported from a Source environment that has a later major or minor version than the target.

66
Q

What is the down leveling functionality?

A

To enable users to export a Solution intended to be imported on a system that has an earlier version. Users can remove non supported components or properties.

67
Q

What is an entity?

A

It is a type of record, such as Account, Case, Product or Goal Metric.

68
Q

What happens when you create an entity in CRM?

A

CRM creates a table in the SQL database to store records that users create and each record is stored in a row of that table.

69
Q

Why do we call it an entity? Instead of a table?

A

Entity also includes other metadata that describes how records are displayed to users. When you expand an entity node in explorer; you’ll see other components such as ; fields, forms, views, charts

70
Q

The Metadata components of an entity are presented as a part of the entity, but are not all parts of it. Explain.

A

Forms and Charts are store in the SystemForm entity while Views are stored in the SaveQuery entity. Components are stored and related differently depending on the situation.

71
Q

What is a field?

A

A field stores one piece of information about a record. Each field is a column in the table for the entity in an SQL database.

72
Q

Properties about how a field is displayed and users are stored as…?

A

XML metadata.

73
Q

What are forms?

A

Forms define the UI for a single record for data entry and retrieval and the way users will input data and read detailed information about a single record.

74
Q

What do forms describe?

A

Layout of fields, sub-grids, other components.

75
Q

What controls the behaviour of scripts?

A

Event handlers.

76
Q

What are views?

A

Lists of multiple records that are filtered to show only what the user wants to see.

77
Q

A view that is created through customization is not related to what?

A

Not related to an SQL view.

78
Q

What are charts?

A

Describe the layout of a visualization of some data. Always used with a view.

79
Q

How are views and charts used together?

A

View filters the rows and chart displays data about those records.

80
Q

Can you remove individual sub components from the solution directly?

A

No, only the whole entity.

81
Q

When you add an entity to a Solution; what else is also added to the solution explorer?

A

The form, view, chart and field nodes.

82
Q

If you delete a custom component like an unwanted field or view, what happens?

A

It is removed from the whole system. On export, the component is not mentioned anywhere in the XML since it no longer exists.

83
Q

Why is good documentation and clear change management processes important with relation to deleting components?

A

Because when you import a solution that doesn’t include a component, the component isn’t deleted from target system. Meaning you must ensure that the deletion of components must be manually replicated in all environments.

84
Q

What happens when you publish the changes to an entity?

A

All changes to forms, views, charts and fields for the entity will occur.

85
Q

How to publish changes to an entity?

A

Select entity node, click Publish.

86
Q

How to publish non-entity components?

A

Select node for that type of component and click Publish.

87
Q

How do you publish all customizations at the same time?

A

You can select any item in the solution explorer except for an entity node and click Publish all Customizations in the ribbon.

88
Q

In general, you should aim for publishing your items individually or all at once?

A

Individually, especially if you have more than one person making changes to the system.

89
Q

What component has to be activated before they can be used?

A

Processes.

90
Q

What component is immediately updated and enforced as soon as they are saved?

A

Security Roles.

91
Q

When you create a component or subcomponent, it is published when you first save it. You should pay attention to this when you create custom activity entities because…

A

It will be immediately visible to other users.

92
Q

How to check dependencies of a component?

A

Select component in the solution explorer and click Show Dependencies.

93
Q

What happens when you delete a custom entity?

A

Deletes all data records for that entity.

94
Q

To delete one item, you might have to go through several layers of what to achieve your goal?

A

Dependencies.

95
Q

Required components will not what?

A

Will not prevent you from deleting the entity.

96
Q

Required components list shows what?

A

Components required by the component that you select to show dependencies for.

97
Q

Describe three advantages of working inside a new Solution instead of making changes to default Solution directly.

A
  1. Work on select components, document changes easily. 2. Using custom Publisher and prefix, changes you make are ‘tagged” permanently to show their origin. 3. Exported solution will only contain components you have selected to add to it. 4. Can save exported solution package as part of change control records.
98
Q

You create a custom view for an entity and deploy this from development to production system, but later on, users no longer require this view, so you delete this view from the Solution in your development system. What else must you do to remove this view from the production environment?

A

Browse to entity in production system and delete view directly, then publish the entity.

99
Q

What happens if you add the built-in Account entity to a Solution and then try to delete it?

A

You will receive an error message because you can’t delete system entities.

100
Q

You open an existing view for the Contact entity, and use Save as to create a copy, make some changes to the columns and Save and Close the view editor. When you navigate to your Contacts to view your results, what will you find?

A

View appears in list, but has same columns as the view that you copied.

101
Q

You have built a Solution and deployed it to a UAT environment. Stakeholders are happy, and you import unmanaged solution package into Production system. Everything is ok for a few days until users complain some of their forms have lost changes you’ve made. What is the most likely cause of this?

A

Someone has imported another Solution that contains an earlier definition of the forms.