{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!

{QUICK TIP}SOME NEW GEMS ON VIEWS in CRM 2013 and CRM 2015

There has been so many occurrences in CRM 2011 days to show records in which clients have asked for records owned by user and their teams.

In CRM 2013 it is now out of box possible:

See Example on Account entity here:

clip_image002

In CRM 2015, it goes even one more level up:

clip_image004

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!