SnapShot! for Dynamics CRM-The Details

The Details

SnapShot! will connect to any Microsoft Dynamics CRM 2011, 2013, 2015 organization using any of the supported installation types:

  • On Premise
  • On Premise using ADFS/IFD
  • CRM Online
  • CRM Online via Office 365

 

System Settings

140 system setting are documented. Most of these are found in the CRM user interface, while others are only seen internally.

 

Entities

Anything found on the Entity Definition page is documented:

image

 

Worksheet Column Description
Display Name Display Name
Name Logical Name
Plural Name Plural Name
Description Description
Ownership Ownership: User/Team or Organization
Primary Field Name of the Primary field
Areas that display this entity Areas that display this entity
Define as an activity entity Is this entity a custom activity?
Custom Field Is this a custom entity?
Notes Notes (including attachments) can be added to this entity
Activities Activities can be added to this entity
Connections Connections can be added to this entity
Sending Email This entity is email-enabled
Mail Merge This entity can be used with the Mail merge feature
Document Management SharePoint documents can be attached to this entity
Queues This entities record can be added to a queue
Duplicate Detection Duplicate detection is enabled
Auditing Are we auditing this entity
Mobile Express This entity can be seen from Mobile Express
Reading pane in CRM for Outlook Reading pane in CRM for Outlook
Offline capability for CRM for Outlook Offline capability for CRM for Outlook

Fields

Everything found on the Field Definition page is documented. Additional information such as for Form locations, is also included:

image

 

Worksheet Column Description
Entity Display Name Display name of the parent entity
Entity Name Logical name of the parent entity
Display Name Display name
Name Name
Field Type Is the field custom or system-defined
Description Type
Custom Description
Requirement Level Requirement Level
Searchable Searchable
Field Security Field Security
Form Locations The names of the forms which this field has been placed on
Auditing Auditing
Max Length Maximum length (for text and memo fields)
Max Value Maximum value (for numbers)
Min Value Minimum value (for numbers)
Precision Decimal precision (for currency and floating point types)
Format For text field types
Target Record Type Target record type (for lookups)

Relationships

Anything found on the Relationship Definition page is documented for 1:N, N:1, and N:N relationships.

 

Worksheet Column Description
Entity Display Name Display name of the parent entity
Entity Name Logical name of the parent entity
Relationship Type 1:N, N:1, N:N
Primary Entity Name of the Primary entity
Related Entity Related Entity name
Name Logical name for the relationship
Lookup Name Logical name of the lookup field that will be placed on the related entity
Other Entity The first half of the N:N relationship
Current Entity The second half of the N:N relationship
Relationship Entity Name Logical name of the relationship entity. This is what is known as the intersect table.
Primary/Current Entity Display Option 1:N: How will the Primary entity relationship be displayed in the Related entity’s sitemap?N:N: How will the Current entity’s relationship be displayed in the Other entity’s sitemap?
Primary/Current Entity Display Area 1:N: The sitemap group where the Primary entity will be displayed.N:N: The sitemap group where the Current entity will be displayed.
Primary/Current Entity Custom Label The custom label should Display Option be set to Custom.
Primary/Current Entity Display Order The display order for this relationship on the sitemap.
Other Entity Display Option N:N: How will the Other entity’s relationship be displayed in the Current entity’s sitemap?
Other Entity Display Area N:N: The sitemap group where the Other entity will be displayed.
Other Entity Custom Label N:N: The custom label should Display Option be set to Custom.
Other Entity Display Order N:N: The display order for this relationship on the sitemap.
Type of Behavior This is the summary for the Cascade Rules behavior when an operation occurs on the Primary Entity record.
Assign What happens when a record is reassigned.
Share What happens when a record is shared.
Unshare What happens when a record is unshared.
Reparent What happens when a record is reparented.
Delete What happens when a record is deleted.
Merge What happens when a record is merged.

 

Views

Views are documented and include interesting information such as:

Worksheet Column Description
Name View Name
Entity Entity the view is associated with
Type The type of view
Description View description
Default View Is this the default view for the entity
Quick Find Query Is this a quick-find query
Custom Is this a custom or standard view
Layout Column Names Columns shown in the result set
Find Columns Columns used to define the filter criteria

Optionally, you can generate View Detail documents that produce a report that looks like this:

 

Forms

Form information including type, Entity, and name are documented.

 

 

Option Sets

A combined list of Global and Entity Option Sets is documented.

Worksheet Column Description
Entity Display Name Display name of the entity
Entity Logical Name Logical name for the entity
Display Name Display name for the Option Set
Logical Name Logical name for the Option Set
Type Type of Option Set
IsCustom Is this a custom or standard option set.
Label Display label for an option set value
Value Value for an option set value

 

Field Security

Both Field Security Profiles and Field Security Permissions are documented.

 

Security Roles

Security Role and Business unit information is documented along with their privileges.

 

image

User Privileges

The privileges that a user has are a combination of all of their individual security role privileges as well as privileges from any Teams they belong to. This report will show you the final security privileges for each user within the system.

The report is in the same format as the Security Role report.

 

Solutions

Solution information is documented.

Worksheet Column Description
Friendly Name Friendly name of the solution
Description Description
Installed On Installed on date
IsManaged Is this a managed Solution
Publisher Name of the publisher
Version Version number
Modified On Last modified date
Modified By Last modified by user

 

Web Resources

A list of all Web Resources, including their type and solution are documented. For JScript Web Resources the following information is also documented:

  • Entity Name
  • Form Name
  • Field Name
  • Event Name
  • Enabled Library Name
  • Function Name
  • Pass Execution Context
  • Parameters

 

Plugins

Plugin Assemblies and Plugin Steps are documented.

  • Name
  • Description
  • IsManaged
  • IsolationMode
  • Solution
  • ModifiedOn
  • ModifiedBy
  • Path

 

Plugin Steps

  • Plugin Name
  • Message
  • Primary Entity
  • Secondary Entity
  • Filtering Attributes
  • Name
  • Run In User’s Context
  • Execution Order
  • Description
  • Stage
  • Execution Mode
  • Deployment
  • Unsecured Configuration
  • Solution
  • Async Auto Delete
  • Modified On
  • Modified By

 

Processes

All Workflow and Dialog processes are documented.

  • Name
  • Description
  • Primary Entity Display Name
  • Primary Entity Name
  • Scope
  • Category
  • On Demand
  • Trigger On Create
  • Trigger On Delete
  • Trigger On Update Attribute List
  • Owner
  • Modified On
  • Modified By

 

Templates

E-Mail, Contract, and Mail Merge template information is documented.

 

Business Units, Users, Teams and Queues

Relevant information for these components is also documented.

 

Automation Testing Matrix

This report was created to show you what automation, both plug-ins and workflows were running on the entities.  This is really good when doing user acceptance testing.

 

For Developers

We’ve also added some data extracted just for Dynamics CRM developers:

  • A complete list of all of the JavaScript functions found in your JScript web resources.
  • A set of JavaScript functions that allow you to move your OnChange and OnSave events from being configured in the Form Editor, to residing in the OnLoad event. The generated code looks like this:
//
// Entity: account
// Form: Sales Form (Main)
//
function form_OnLoad() {
 Xrm.Page.getAttribute("telephone1").addOnChange(formatPhoneNumber); // new_CommonFunctions 
 Xrm.Page.getAttribute("telephone2").addOnChange(formatPhoneNumber); // new_CommonFunctions 
 Xrm.Page.getAttribute("fax").addOnChange(formatPhoneNumber); // new_CommonFunctions
onLoad(); // new_account_main_sales.js 
}

This is probably an edge-case for some Dynamics CRM Developers, but it saved me quite a bit of time when re-architecting the a fairly large CRM system.