Thursday, December 17, 2015

Microsoft Dynamics CRM Server 2016 (On-Premises) Trial Key


    • Microsoft Dynamics CRM Workgroup Server 2016 (5 CAL limit): D8W6N-FJXJF-CC3TK-6CMGV-VVBH9
    • Microsoft Dynamics CRM Server 2016 (no CAL limit): WCPQN-33442-VH2RQ-M4RKF-GXYH4

Thursday, November 26, 2015

Recalculate Rollup Fields - Dynamics CRM 2015 Programatically (Plugin)

using Microsoft.Crm.Sdk.Messages;
      


CalculateRollupFieldRequest CRF = new CalculateRollupFieldRequest
                    {
                       Target = new EntityReference("ParentEntityName", ParentEntityNameID),
                        FieldName = "FieldName"
                    };

                  

 CalculateRollupFieldResponse response = (CalculateRollupFieldResponse)service.Execute(CRF);

Sunday, July 19, 2015

CRM 2013/15 On-Prem - Last access date & time for CRM users

For getting a list of all last login date and time for all CRM users on Dynamics CRM (On-Premises), run below SQL script using SQL Server Management Studio :

SELECT SU.FullName
 ,SU.DomainName
 ,SUO.LastAccessTime
FROM SystemUser SU
INNER JOIN [MSCRM_CONFIG].[dbo].[SystemUserOrganizations] SUO ON SUO.CrmUserId = SU.SystemUserId
INNER JOIN [MSCRM_CONFIG].[dbo].[SystemUserAuthentication] SUA ON SUA.UserId = SUO.UserId
ORDER BY SUO.LastAccessTime DESC



Friday, July 17, 2015

Applying same Business Rule to several forms, not all forms

We can configure Business Rules to be used on all forms for an entity, or only on one form. If you want to apply a Business Rule to several forms, and not all forms, you must create a copy of the rule for each form,you can do this by opening the Business Rule and clicking Deactivate then Save As and entering a new name for the copy of the Business Rule and select the scope and active it.









And if you select all forms as the scope of a Business Rule, the rule will be applied to all forms (Main or Quick Create forms), and you can not select the scope for a rule to apply to the Quick Create form only!





Import Data Wizard for CRM 2015 Online Update 1 now supporting XLSX file format!

The Microsoft Dynamics CRM 2015 Online Update 1 encapsulates many new great features and improvements. One of such features is improved Import Data Wizard to support XLSX file format.


Monday, July 13, 2015

List of all custom fields names & types for any Custom Entity - Dynamics CRM On-Premises

For getting a list of all custom fields names and types for any Dynamics CRM (On-Premises) custom entity, run below SQL script using SQL Server Management Studio :

USE [CRMDatabaseName]

SELECT c.NAME
 ,t.NAME
FROM syscolumns c
INNER JOIN sys.types t ON t.system_type_id = c.xtype
WHERE id = object_id('CustomEntityTableName')
 AND c.NAME LIKE 'new_%'


Note : Replace new with your solution prefix  :)
          Remove (and c.name LIKE 'new_%') for getting all of custom and system fields.

Saturday, June 27, 2015

List of supported languages by Microsoft Dynamics CRM 2015


# Language Name LCID
1 Arabic 1025
2 Basque (Basque) 1069
3 Bulgarian (Bulgaria) 1026
4 Catalan (Catalan) 1027
5 Chinese (Hong Kong S.A.R.) 3076
6 Chinese (PRC) 2052
7 Chinese (Taiwan) 1028
8 Croatian (Croatia) 1050
9 Czech 1029
10 Danish 1030
11 Dutch 1043
12 English 1033
13 Estonian (Estonia) 1061
14 Finnish 1035
15 French 1036
16 Galician (Galician) 1110
17 German 1031
18 Greek 1032
19 Hebrew 1037
20 Hindi (India) 1081
21 Hungarian 1038
22 Indonesian 1057
23 Italian 1040
24 Japanese 1041
25 Kazakh (Kazakhstan) 1087
26 Korean 1042
27 Latvian (Latvia) 1062
28 Lithuanian (Lithuania) 1063
29 Malay 1086
30 Norwegian (Bokmål) 1044
31 Polish 1045
32 Portuguese (Brazil) 1046
33 Portuguese (Portugal) 2070
34 Romanian (Romania) 1048
35 Russian 1049
36 Serbian (Cyrillic) 3098
37 Serbian (Latin, Serbia) 2074
38 Slovak (Slovakia) 1051
39 Slovenian (Slovenia) 1060
40 Spanish 3082
41 Swedish 1053
42 Thai 1054
43 Turkish 1055
44 Ukrainian (Ukraine) 1058
45 Vietnamese 1066

Friday, June 26, 2015

Arabic Language Pack For Microsoft Dynamics CRM 2015

By looking to the Language Packs list for Microsoft Dynamics CRM 2015 at Microsoft download center,you will not find Arabic Language Pack at the list.



So, don't waste your time searching for it, I'm sharing with you a direct link for downloading Arabic Language Pack For Microsoft Dynamics CRM 2015

Monday, June 22, 2015

Do not use the name of the entity as the display name of the primary field.


When you create an entity, the primary key field that contains the unique record ID (GUID) has the same display name as the original display name of the entity. If your Primary Field uses the same Display Name, this is allowed because the schema names will be different (the primary key field will be called <prefix>_<entityname>id).

When you are trying to use fields in advanced find queries, charts and workflows, for example, the two fields appear identical, and this could lead to confusion and possible errors. It is useful to be able to rely on the fact that the field that has the same name as the entity is the primary key field in every case. Therefore, we recommend that you select something different, or accept the default value of “Name”

Friday, April 17, 2015

The field has an invalid XAML formula definition - Rollup field

Issue resolution

Recently came across an interesting issue from one of my colleagues, when he tried to create a rollup field, a message is telling that XAML formula definition for rollup field is invalid. 




A little tracing and checking made me suspect that he did something wrong on creating the rollup field, and I was a bit surprised!

So what is the best way to resolve it?

By using MSSQL profiler I got that the relationship schema name for the parent and child entities was too long.





After researching a little bit, I found that the schema name and logical name for custom entities, attributes, relationships and for many-to-many relationship intersect tables have a maximum length of 50 characters.


Hope it helps!

Unexpected Error When Replying or Forwarding an Email

Recently came across an interesting issue from one of my clients, they were working fine since around 2 years ago with no issues, using Dyn...