Abed Haniyah: June 2015

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”