feridun

To sort rows in a dataset you can choose a column in the dataset in the properties of the tablix or other report element. Or if you need a custom sort where the sorting isn’t alphabetical or numerical you can add code to the report and then call the code in an expression in the sorting […]

If you have installed CRM 2013 for Outlook and then need to go back to CRM 2011 for Outlook, perform these steps: Uninstall CRM 2013 for Outlook Delete the program folder, the default location is C:\Program Files\Microsoft Dynamics CRM (or C:\Program Files (x86)\Microsoft Dynamics CRM for a 32-bit install on a 64-bit computer). Delete the

Email correlation is a process where CRM links tracked emails with records in the database based on information in the email. In earlier versions, Smart Matching and Tracking Tokens were used to correlate emails. Microsoft Dynamics CRM 2013 introduces a new method to match emails which uses information in email headers. It is claimed that

Microsoft Dynamics CRM 2013 introduces encryption of password fields in the SQL database. Encryption is performed at the organization level and the keys are stored in the OrganizationProperties table in MSCRM_CONFIG. There are two rows for each organization. In each row the columns shown in the table below are populated. Column Notes ID Organization ID

When the ADFS Token-sgining and Token-Decrypting certificates in ADFS are automatically renewed, users in CRM might not be able to login. They receive HTTP 401 Unauthorized Access is denied errors. This occurs because CRM is still using the expired ADFS token certificates. To resolve this reconfigure Claims-based Authentication and Internet-Facing deployment in CRM. This article

In CRM 2011, isv.config is not used to store custom buttons, tabs and menus as in earlier versions. The only item that I think isv.config is used for is to customize the appearance of the service calendar.

For CRM 2011, see this article. The following table details Update Rollups released for Microsoft Dynamics CRM 2013. Note that some Update Rollups cannot be installed, so a backup before installation is advised. For CRM 2013 on-premise, the third number in the build is the same as the Update Rollup number. A separate set of update

CRM has several deployment wide settings which are stored in the DeploymentProperties table in the configuration database (usually MSCRM_CONFIG). It is not recommended to modify the values in the table directly you may sometimes need to change values. The recommended method is usually to use a PowerShell script. Some of the settings are described in the following