{USEFUL to KNOW}CRM 2015 exams and courseware links

Below is a list of resources if you are planning on sitting your Microsoft Dynamics 2015 Exams.

As more information becomes available I will update this post.

If you find additional resources  feel free to let me know in the comments.

I have listed each Exam followed by the courses you will need to study to take the Exam.

Microsoft now has a NEW eLearning site http://itacademy.microsoft.com you can access it via your CustomerSource Account or PartnerSource Account.

Dynamics CRM 2015 Exams

Microsoft Dynamics CRM 2015 Installation

Exam MB2-708 Microsoft Dynamics CRM 2015 Installation

  • Course 80679: Installation in Microsoft Dynamics CRM 2015 [eLearning]
  • Course 80664: Deployment in Microsoft Dynamics CRM Online [eLearning]
Microsoft Dynamics CRM 2015 Applications
  • Course 80667: Introduction to Microsoft Dynamics CRM Online [eLearning]
  • Course 80669: Sales and Marketing in Microsoft Dynamics CRM Online [eLearning]
  • Course 80668: Customer Service in Microsoft Dynamics CRM Online [eLearning]
Customization and Configuration in Microsoft Dynamics CRM Online and On Premise
  • Course 80665: Customization and Configuration in Microsoft Dynamics CRM Online and On Premise [eLearning]
Reporting in Microsoft Dynamics CRM Online
  • Course 80675: Reporting in Microsoft Dynamics CRM Online [eLearning]
Social Listening for Microsoft Dynamics CRM Online
  • Course 80676: Social Listening for Microsoft Dynamics CRM Online [eLearning]
Microsoft Dynamics Marketing

Exam MB2-720 Applications in Microsoft Dynamics Marketing [Available on Pearson VUE]

  • Course 80677: Functional Application in Microsoft Dynamics Marketing [eLearning]
  • Course 80678: Technical Deployment and Customization in Microsoft Dynamics Marketing [eLearning]

Dynamics Partner specific learning site Dynamics Learning Portal and link to the corresponding FAQ (including how to get access):

 https://mbspartner.microsoft.com/faq

and the latest and greatest certifications including their codes:

MB2-704: Microsoft Dynamics CRM Application

· MB2-706: Microsoft Dynamics CRM Online Deployment

· MB2-707: Microsoft Dynamics CRM Customization and Configuration

· MB2-708: Microsoft Dynamics CRM Installation

· MB2-720: Functional Application in Microsoft Dynamics Marketing

All of them should be available from Person VUE: https://www.microsoft.com/learning/en-us/exam-list.aspx and here http://www.pearsonvue.com/microsoft/

Hope it helps!

Advertisements

CRM 2015 Deprecated MESSAGES

There is very good documentation available for deprecated client side code, but very less on deprecated server side messages.

Here is a helpful list:

CRM 2015 messages which are deprecated:

Class
Description
AddProductToKitRequest Deprecated. Use the ProductAssociation entity. Contains the data that is needed to add a product to a kit.
AddProductToKitResponse Deprecated. Use the ProductAssociation entity. Contains the response from the AddProductToKitRequest class.
AddSubstituteProductRequest Deprecated. Use the AssociateRequest class. Adds a link between two entity instances in a many-to-many relationship.
AddSubstituteProductResponse Deprecated. Use the AssociateRequest class and its associated response class. Contains the response from the AddSubstituteProductRequest class.
AssociateEntitiesRequest Deprecated. Use the AssociateRequest class. Contains the data that is needed to add a link between two entity instances in a many-to-many relationship.
AssociateEntitiesResponse Deprecated. Use the AssociateRequest class and its associated response class. Contains the response from the AssociateEntitiesRequest class.
CompoundCreateRequest Deprecated. Use the CreateRequest class. Creates a compound entity, such as a sales order (order), invoice, quote, or duplicate rule (duplicate detection rule); and its related entity, such as a sales order detail (order product), invoice detail (invoice product), quote detail (quote product), or duplicate rule condition.
CompoundCreateResponse Deprecated. Use the CreateRequest class and its associated response class.
CompoundUpdateRequest Deprecated. Use the CreateRequest class. Contains the data that is needed to update a compound record, such as a sales order (order), invoice, quote, or duplicate rule (duplicate detection rule); and its related detail record, such as a sales order detail (order product), invoice detail (invoice product), quote detail (quote product), or duplicate rule condition.
CompoundUpdateResponse Deprecated. Use the CreateRequest class and its associated response class. Contains the response from the CompoundUpdateRequest class.
ConvertKitToProductRequest Deprecated. Contains the data that is needed to convert a kit to a product.
ConvertKitToProductResponse Deprecated. Contains the response from the ConvertKitToProductRequest class.
ConvertProductToKitRequest Deprecated. Contains the data that is needed to convert a product to a kit.
ConvertProductToKitResponse Deprecated. Contains the response from the ConvertProductToKitRequest class.
DisassociateEntitiesRequest Deprecated. Use the DisassociateRequest class. Contains the data that is needed to remove a link between two entity instances in a many-to-many relationship.
DisassociateEntitiesResponse Deprecated. Use the DisassociateRequest class and its associated response class. Contains the response from the DisassociateEntitiesRequest class.
ExecuteFetchRequest Deprecated. Use the RetrieveMultipleRequest class.
ExecuteFetchResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class.
IsBackOfficeInstalledRequest Deprecated. Checks whether Microsoft Dynamics GP 9.0 is installed.
IsBackOfficeInstalledResponse Deprecated.
MakeAvailableToOrganizationReportRequest Deprecated. Use the UpdateRequest class.
MakeAvailableToOrganizationReportResponse Deprecated. Use the UpdateRequest class and its associated response class.
MakeAvailableToOrganizationTemplateRequest Deprecated. Use the UpdateRequest class.
MakeAvailableToOrganizationTemplateResponse Deprecated. Use the UpdateRequest class and its associated response class.
MakeUnavailableToOrganizationReportRequest Deprecated. Use the UpdateRequest class.
MakeUnavailableToOrganizationReportResponse Deprecated. Use the UpdateRequest class and its associated response class.
MakeUnavailableToOrganizationTemplateRequest Deprecated. Use the UpdateRequest class.
MakeUnavailableToOrganizationTemplateResponse Deprecated. Use the UpdateRequest class and its associated response class.
RemoveProductFromKitRequest Deprecated. Use the ProductAssociation entity. Contains the data that is needed to remove a product from a kit.
RemoveProductFromKitResponse Deprecated. Use the ProductAssociation entity. Contains the response from the RemoveProductFromKitRequest.
RemoveSubstituteProductRequest Deprecated. Use the ProductSubstitute entity.
RemoveSubstituteProductResponse Deprecated. Use the ProductSubstitute entity.
RetrieveMembersTeamRequest Deprecated. Use the RetrieveMultipleRequest class.
RetrieveMembersTeamResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class. Contains the response from the RetrieveMembersTeamRequest class.
RetrieveSubsidiaryTeamsBusinessUnitRequest Deprecated. Use the RetrieveMultipleRequest class.Contains the data needed to retrieve a collection of entity instances based on the specified query criteria.
RetrieveSubsidiaryTeamsBusinessUnitResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class.
RetrieveSubsidiaryUsersBusinessUnitRequest Deprecated. Use the RetrieveMultipleRequest class.Contains the data needed to retrieve all user information from the child business units of the specified business unit.
RetrieveSubsidiaryUsersBusinessUnitResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class.Contains the response from the RetrieveSubsidiaryUsersBusinessUnitRequest message.
RetrieveTeamsSystemUserRequest Deprecated. Use the RetrieveMultipleRequest class.Contains the data needed to retrieve the list of teams of which the specified user is a member.
RetrieveTeamsSystemUserResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class.Contains the response from the RetrieveTeamsSystemUserRequest message.
RetrieveUserSettingsSystemUserRequest Deprecated. Use the RetrieveMultipleRequest class.Contains the data needed to retrieve the user settings for the specified system user (user).
RetrieveUserSettingsSystemUserResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class.
UpdateUserSettingsSystemUserRequest Deprecated. Use the UpdateRequest class.
UpdateUserSettingsSystemUserResponse Deprecated. Use the UpdateRequest class and its associated response class.

 

Hope it helps!

{STEP BY STEP} YAMMER INTEGRATION WITH CRM 2013

Yammer Integration

Prerequisites:

· Please add below site to Internet Explorer à Option à Security à Trusted Site:

o https://*.crm.dynamics.com

o https://www.yammer.com

clip_image002

· Yammer Enterprise: Integrating Yammer with CRM 2013 requires the enterprise version of Yammer

· The user performing the integration with Yammer requires system administrator privileges in CRM 2013

· The user performing the integration with Yammer requires system administrator privileges for your organization’s Yammer account

Please follow the below steps to setup the Yammer Integration:

  1. Login to Dynamics CRM 2013 and navigate to the Settings area. This is done by clicking on Microsoft Dynamics CRM à Settings
  2. Navigate to the Administration section by clicking on Settings à Administration
  3. Click on the link titled Yammer Configuration to begin the wizard steps to enable the integration. Please note that you will not see this link if you do not have System Administrator privileges in Dynamics CRM
    clip_image004
  1. A Yammer Disclaimer page will display, asking you to agree to the disclaimer. Click on Continue to proceed
    clip_image006
  2. A configuration page will appear, with steps listed on how to connect your Yammer environment to Dynamics CRM 2013. Notice that only the first step, Authorize Microsoft Dynamics CRM Online to connect to Yammer will be enabled at this point. Click on this link to perform the authorization step
    clip_image008
  3. A dialog will display requesting you enter your Yammer credentials for the authorization. Enter these credentials and click the Log In button
    clip_image010
  4. Another dialog will be displayed that asks you to confirm the connection between Yammer and Dynamics CRM 2013. Click on the Allow button to allow this connection
  5. At this point the integration is performed and complete, but the process takes you back to the Yammer configuration page, and you will notice that steps 2 and 3 are now enabled. These are optional steps that you can configure for specific items/behavior with the Yammer integration
    clip_image012
  6. [Optional] – Select a Yammer Group ID to control conversation access. This optional step allows you to configure whether all the conversations initiated from Dynamics CRM should be placed in a specific group in Yammer. If you don’t specify a group, the All Company Group is used for this
  7. [Optional] Set the level of security for Yammer activity stream messages. This optional step allows you to configure whether the conversations in Dynamics CRM are visible to everyone (Public). Selecting Private for this setting will require users in Dynamics CRM to follow the appropriate record in order to see the Yammer conversations
  8. Once Yammer has been connected to Dynamics CRM 2013, you need to specify which entities in CRM you wish to enable for use with Yammer. This can be done by navigating to the Post Configuration section in Settings (click Settings àPost Configurations).
  9. In order to activate an entity for use with Yammer, select the desired entity and click the Activate selection in the top navigation bar. Deactivating an entity for use with Yammer is done by clicking the Deactivate selection in the top navigation bar. Please make sure you Publish All Customizations to verify that the changes you made take effect in Dynamics CRM.

clip_image014

  1. To enable record types and rules to automatically trigger a Yammer post, click or tap Edit message rules.

clip_image016

  1. To trigger Yammer posts, enable or disable rules.

clip_image018

  1. Yammer posts are now part of Microsoft Dynamics CRM Online.

clip_image020

  1. Great, you are done!

Hope it helps!

{New Information} CRM Monitoring service: CRM 2013 and CRM 2015

The Microsoft Dynamics CRM Monitoring Service is an NT-style service that monitors all Microsoft Dynamics CRM Server roles running on the local computer. The Monitoring Service doesn’t transmit information outside the computer where the service is running. The Monitoring Service is installed with the installation of any Microsoft Dynamics CRM Server role.
The monitoring service validates the health of the server roles that are running on the local computer by running a series of tests. By default, monitoring occurs every 15 minutes and 10 records are maintained before the earliest record is replaced. Some tests performed by the monitoring service require that the organization be set for monitoring.
View monitoring results
Events are recorded under the MSCRMMonitoringServerRole source in the Application area of Event Viewer.
By default, detailed monitoring results are saved as XML files located in C:\Program Files\Microsoft Dynamics CRM\Monitoring\results.

Tip: Use a web browser to view the monitoring logs. To do this in Internet Explorer, right-click the monitoring XML file, select Open with, and then select Internet Explorer.

Additionally, you can record monitoring results to the configuration database as described later in this topic. Then you can use a SQL statement such as the following to view monitoring information for the deployment.
USE MSCRM_CONFIG SELECT * FROM MonitoringResults ORDER BY EndTime
Change monitoring settings
The following PowerShell commands perform these operations.
•    Displays the current monitoring settings.
•    Sets the monitoring service to record a maximum of 10 results to the MonitoringResults table in the configuration database (MSCRM_CONFIG) in addition to recording to XML files in a file folder.

Sets the testorg organization for organization-level monitoring, and sets the monitoring organization user account and password.
•    Displays the current monitoring settings, again.
Note: Although this example configures two separate options, you don’t have to configure both options together. The first option is to store monitoring records in the configuration database, and the second option is to set the monitoring organization, account, and password.
Using PowerShell:
Add-PSSnapin Microsoft.Crm.PowerShell
Get-CrmSetting -SettingType MonitoringSettings
$set =Get-CrmSetting -SettingType Monitoringsettings
$set.StoreResultsInDatabase = “true”
$set.ResultsToKeepInDatabase = “10”
$set.MonitoringOrganizationUniqueName =”testorg”
$set.MonitoringOrganizationUserAccount = “contoso\administrator”
$set.MonitoringOrganizationUserPassword = “password”
Set-CrmSetting -Setting $set
Get-CrmSetting -SettingType MonitoringSettings

Important: After you make a change to the monitoring service settings, you may need to restart the Microsoft Dynamics CRM Monitoring Service to incorporate the change.

Opening in Excel, excel file is more readable, intentionally skipped some columns:

image

Hope it helps!

Fiscal date query operators in FetchXML

A FetchXML query in Microsoft Dynamics CRM 2015 and Microsoft Dynamics CRM Online 2015 Update can use special fiscal date values in queries. For example, a FetchXML query can find all orders fulfilled in the last fiscal month.

noteNote

The FetchXML query uses the organization’s fiscal year settings for all fiscal date queries.

Using FetchXML fiscal date conditional operators

The following example shows a FetchXML expression that finds all orders fulfilled in the last fiscal period, according to the organization’s fiscal year settings. For example, if the organization uses fiscal months, the query returns orders fulfilled in the last fiscal month. If the organization uses fiscal quarters, the query returns orders fulfilled in the last fiscal quarter. If the organization uses fiscal semesters, orders fulfilled in the last fiscal semester are returned.

XML

<fetch> <entity name="order">  <attribute name="name"/>  <filter type="and">   <condition attribute="datefulfilled"              operator="last-fiscal-period"/>  </filter> </entity></fetch>

The following example shows a FetchXML expression that finds all accounts created in fiscal year 2013.

XML

<fetch> <entity name="account">  <attribute name="name"/>  <filter type="and">   <condition attribute="createdon"              operator="in-fiscal-year"              value="2013"/>  </filter> </entity></fetch>

The following example shows a FetchXML expression that finds all opportunities with an estimated close date in the next three fiscal years, based on the organization’s fiscal year settings. The value for x is specified in the value attribute of the condition tag.

XML

<fetch> <entity name="opportunity">  <attribute name="name"/>  <filter type="and">   <condition attribute="estimatedclosedate"              operator="next-x-fiscal-years"              value="3"/>  </filter> </entity></fetch>

The following example shows a FetchXML expression that finds all orders fulfilled in period three of any fiscal year, according to the organization’s fiscal year settings. The fiscal period value is specified in the value attribute of the condition tag. If the organization uses fiscal months, the query returns results from month three. If the organization uses fiscal quarters, the query returns results from quarter three. If the organization uses fiscal semesters, no results are returned; there are only two semesters, and the value supplied is therefore out-of-range.

XML

<fetch> <entity name="order">  <attribute name="name"/>  <filter type="and">   <condition attribute="datefulfilled"              operator="in-fiscal-period"              value="3"/>  </filter> </entity></fetch>

The following example shows a FetchXML expression that finds all orders fulfilled in period three of fiscal year 2013, according to the organization’s fiscal year settings. If the organization uses fiscal months, the query returns results from month three. If the organization uses fiscal quarters, the query returns results from quarter three. If the organization uses fiscal semesters, no results are returned; there are only two semesters, and the value supplied is therefore out-of-range.

XML

<fetch> <entity name="order">  <attribute name="name"/>  <filter type="and">   <condition attribute="datefulfilled"              operator="in-fiscal-period-and-year">    <value>3</value>    <value>2013</value>   </condition>  </filter> </entity></fetch>

The following example shows a FetchXML aggregation expression that sums the total amount of orders fulfilled and groups the result by fiscal semester and fiscal year.

XML

<fetch aggregate="true"> <entity name="order">  <attribute name="totalamount"             aggregate="sum"             alias="total"/>  <attribute name="datefulfilled"             groupby="true"             dategrouping="fiscal-period"/> </entity></fetch>

Source: TECHNET

Hope it helps!