When you export plugin, you need to export plugin's steps too. The steps are called Sdk Message Processing Steps.
Plugin Deployment in CRM 2011 - Best Practices
http://crmdm.blogspot.co.nz/2011/03/plugin-deployment-in-crm-2011-best.html
Showing posts with label Crm 2011. Show all posts
Showing posts with label Crm 2011. Show all posts
Tuesday, 31 January 2012
Sunday, 29 January 2012
Create a Crm console app from scratch.
*Set the project's Target framework to be .Net Framework 4.
*To interact with Crm 2011 API, you can either refer to CRM 2011 sdk binary files or Service Reference
+ If you want to use sdk binary files: Include the
Microsoft.Crm.Sdk.Proxy.dll
Microsoft.Xrm.Sdk.dll in project reference
System.Security
System.Runtime.Serialization
and System.ServiceModel (This is for using WCF)
+ If you want to use Service Reference: Download the Organization Service endpoint from the Crm Developer Resources page.
*Reference the namespaces in the code.
using System.ServiceModel; // For using the WCF
using System.ServiceModel.Description; // You need this to use the ClientCredential class.
//Contains enumerations of possible picklists and integer values for some attributes.
//The naming convention of the classes is to make it easier to locate the specific attribute.
using Microsoft.Crm.Sdk;
//Defines the data contracts for attribute types, interfaces for authoring plug-ins,
//and other general purpose xRM types and methods.
using Microsoft.Xrm.Sdk;
//Defines classes for use by client-code, including a data context,
//proxy classes to ease the connection to Microsoft Dynamics CRM, and the LINQ provider.
using Microsoft.Xrm.Sdk.Client;
// Defines request/response classes for Create, Retrieve, Update, Delete, Associate , Disassociate, and the metadata classes.
using Microsoft.Xrm.Sdk.Messages;
// Defines query classes required to connect to Microsoft Dynamics CRM.
using Microsoft.Xrm.Sdk.Query;
Microsoft.Crm.Sdk.Messages;
The namespaces required for doing a WhoAmIRequest are Microsoft.Crm.Sdk, Microsoft.Xrm.Sdk.Client, Microsoft.Crm.Sdk.Messages, System.ServiceModel, System.ServiceModel.Description.
* Include the deviceidmanager.cs file in the project for authentication. Your can find the class in the crm sdk helper folder \\SDK CRM 2011\sdk\samplecode\cs\helpercode\deviceidmanager.cs.
+ Also include the Microsoft.Crm.Services.Utility namespace.
* Setup the credential which will be used to connect to Crm WCF endpoint
* Connect to WCF endpoint
* Require early bound type support
* Do something with theh endpoint
*To interact with Crm 2011 API, you can either refer to CRM 2011 sdk binary files or Service Reference
+ If you want to use sdk binary files: Include the
Microsoft.Crm.Sdk.Proxy.dll
Microsoft.Xrm.Sdk.dll in project reference
System.Security
System.Runtime.Serialization
and System.ServiceModel (This is for using WCF)
+ If you want to use Service Reference: Download the Organization Service endpoint from the Crm Developer Resources page.
*Reference the namespaces in the code.
using System.ServiceModel; // For using the WCF
using System.ServiceModel.Description; // You need this to use the ClientCredential class.
//Contains enumerations of possible picklists and integer values for some attributes.
//The naming convention of the classes is
using Microsoft.Crm.Sdk;
//Defines the data contracts for attribute types, interfaces for authoring plug-ins,
//and other general purpose xRM types and methods.
using Microsoft.Xrm.Sdk;
//Defines classes for use by client-code, including a data context,
//proxy classes to ease the connection to Microsoft Dynamics CRM, and the LINQ provider.
using Microsoft.Xrm.Sdk.Client;
// Defines request/response classes for Create, Retrieve, Update, Delete, Associate , Disassociate, and the metadata classes.
using Microsoft.Xrm.Sdk.Messages;
// Defines query classes required to connect to Microsoft Dynamics CRM.
using Microsoft.Xrm.Sdk.Query;
Microsoft.Crm.Sdk.Messages;
The namespaces required for doing a WhoAmIRequest are Microsoft.Crm.Sdk, Microsoft.Xrm.Sdk.Client, Microsoft.Crm.Sdk.Messages, System.ServiceModel, System.ServiceModel.Description.
* Include the deviceidmanager.cs file in the project for authentication. Your can find the class in the crm sdk helper folder \\SDK CRM 2011\sdk\samplecode\cs\helpercode\deviceidmanager.cs.
+ Also include the Microsoft.Crm.Services.Utility namespace.
* Setup the credential which will be used to connect to Crm WCF endpoint
* Connect to WCF endpoint
* Require early bound type support
* Do something with theh endpoint
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.ServiceModel; // For using the WCF
using System.ServiceModel.Description;
// Contains enumerations of possible picklists and integer values for some attributes.
// The naming convention of the classes is [open arrow brace]entityname[close arrow brace][open arrow brace]attributename[close arrow brace] to make it easier to locate the specific attribute.
using Microsoft.Crm.Sdk;
// Defines the data contracts for attribute types, interfaces for authoring plug-ins,
// and other general purpose xRM types and methods.
//using Microsoft.Xrm.Sdk;
// Defines classes for use by client-code, including a data context,
// proxy classes to ease the connection to Microsoft Dynamics CRM, and the LINQ provider.
using Microsoft.Xrm.Sdk.Client;
// Defines request/response classes for Create, Retrieve, Update, Delete, Associate , Disassociate, and the metadata classes.
//using Microsoft.Xrm.Sdk.Messages;
// Defines query classes required to connect to Microsoft Dynamics CRM.
//using Microsoft.Xrm.Sdk.Query;
using Microsoft.Crm.Services.Utility;
using Microsoft.Crm.Sdk.Messages;
namespace CrmConsoleApplication1
{
class Program
{
private static OrganizationServiceProxy _serviceProxy;
private static ClientCredentials _clientCreds;
//private static ClientCredentials _deviceCreds;
static void Main(string[] args)
{
// Setup credential
_clientCreds = new ClientCredentials();
_clientCreds.Windows.ClientCredential.UserName = "Administrator";
_clientCreds.Windows.ClientCredential.Password = "NotTheRealPassword";
_clientCreds.Windows.ClientCredential.Domain = "PLAYGROUND";
// The DeviceIdManager class registers a computing device with Windows Live ID, through the generation of a device ID and password,
// and optionally stores that information in an encrypted format on the local disk for later reuse.
// This will fail here as this vm don't have access to the Internet therefore there is no way for it to generate a device ID with login.live.com
//_deviceCreds = DeviceIdManager.LoadOrRegisterDevice();
// Connect to Crm WCF endpoint
using (_serviceProxy = new OrganizationServiceProxy(new Uri("http://localhost:5555/CRM2011RTM/XRMServices/2011/Organization.svc"),
null,
_clientCreds,
null))
{
// require early bound type support
_serviceProxy.ServiceConfiguration.CurrentServiceEndpoint.Behaviors.Add(new ProxyTypesBehavior());
OrganizationServiceContext orgContext = new OrganizationServiceContext(_serviceProxy);
WhoAmIRequest request = new WhoAmIRequest();
WhoAmIResponse response = (WhoAmIResponse)orgContext.Execute(request);
Console.WriteLine("Your Crm user Guid is {0}", response.UserId);
}
Console.Read();
}
}
}
Saturday, 28 January 2012
CRM 2011: IntelliSense for Xrm.Page
http://www.patrickverbeeten.com/pages/ContentItemPage.aspx?id=31&item=118&p=true
In CRM 2011 Javascript is no longer embedded in forms but now has build in feature to use external resource files. You can edit these files using the web browser or in an external editor. Visual studio supports Intellisense for JavaScript, this explains how enable the support for the CRM provided objects such as the Xrm.Page object to be shown.
To enable this support Visual Studio needs a reference to base the IntelliSense. First you need to download the reference file XrmPage-vsdoc.js (right click and choose save). Save this file on a convinient location. Now you can create a new js file in Visual Studio then add the following line to the top of this file:
///
The path to the file can either be relative or absolute, in this example the reference file is placed in a folder named IntelliSense in the folder where the new web resource js file is saved.
I have only tried this file with Visual Studio 2010. If there are any function which are incorrect or other errors please let me know.
This file is distributed as Freeware for details see here or the license contained in the file.
On this site http://crm2011snippets.codeplex.com you can download a set of snippets to automate common functions for JavaScript used with CRM.
In CRM 2011 Javascript is no longer embedded in forms but now has build in feature to use external resource files. You can edit these files using the web browser or in an external editor. Visual studio supports Intellisense for JavaScript, this explains how enable the support for the CRM provided objects such as the Xrm.Page object to be shown.
To enable this support Visual Studio needs a reference to base the IntelliSense. First you need to download the reference file XrmPage-vsdoc.js (right click and choose save). Save this file on a convinient location. Now you can create a new js file in Visual Studio then add the following line to the top of this file:
///
The path to the file can either be relative or absolute, in this example the reference file is placed in a folder named IntelliSense in the folder where the new web resource js file is saved.
I have only tried this file with Visual Studio 2010. If there are any function which are incorrect or other errors please let me know.
This file is distributed as Freeware for details see here or the license contained in the file.
On this site http://crm2011snippets.codeplex.com you can download a set of snippets to automate common functions for JavaScript used with CRM.
Wednesday, 25 January 2012
How to change crm 2011 online session timeout?
(On the ADFS server?)Open a Windows PowerShell window with Administrative Rights.
PS > Add-PSSnapin Microsoft.Adfs.PowerShell
PS > Get-ADFSRelyingPartyTrust -Name:”relying_party“
PS > Set-ADFSRelyingPartyTrust -TargetName “your_relying_party_name” -TokenLifetime 7200
So this code set the session timeout as 12 Hours (7200 minutes )
Don’t forget to replace your_relying_party_name with the real name in your AD FS 2 Manager –>Relying Party Trusts
http://www.interactivewebs.com/blog/index.php/server-tips/your-session-in-microsoft-dynamics-crm-is-about-to-expire-crm-2011-extend-session-time/
http://www.isvlabs.com/2011/11/how-to-set-dynamics-crm-2011-ifd-session-timeout/
PS > Add-PSSnapin Microsoft.Adfs.PowerShell
PS > Get-ADFSRelyingPartyTrust -Name:”relying_party“
PS > Set-ADFSRelyingPartyTrust -TargetName “your_relying_party_name” -TokenLifetime 7200
So this code set the session timeout as 12 Hours (7200 minutes )
Don’t forget to replace your_relying_party_name with the real name in your AD FS 2 Manager –>Relying Party Trusts
http://www.interactivewebs.com/blog/index.php/server-tips/your-session-in-microsoft-dynamics-crm-is-about-to-expire-crm-2011-extend-session-time/
http://www.isvlabs.com/2011/11/how-to-set-dynamics-crm-2011-ifd-session-timeout/
Wednesday, 18 January 2012
Connect to Crm 2011 WCF interface via code
Library needed
The project will need to use .Net4 profile.
Using needed
Get Service method
var creds = new ClientCredentials(); //Get your current login
The project will need to use .Net4 profile.
Using needed
Get Service method
var creds = new ClientCredentials(); //Get your current login
Monday, 16 January 2012
Generate code with crmsvcutil #crmsvcutil extension #OrganizationServiceContext #OrganizationServiceContext
Syntax
CrmSvcUtil.exe /url:http:////XRMServices/2011/Organization.svc
/out:.cs /username: /password: /domain:
/namespace: /serviceContextName:
An example for generating early bound entities with a service context
CrmSvcUtil.exe ^
/url:http://localhost:5555/Crm2011RTM/XRMServices/2011/Organization.svc ^
/out:Xrm.cs ^
/language:CS ^
/domain:playground ^
/username:user-defined-usrname ^
/password:user-defined-pwd ^
/namespace:Xrm ^
/servicecontextname:XrmServiceContext
::The following para will only work if you run this bat file in the sdk\bin folder due to required dlls.
::/codeCustomization:"Microsoft.Xrm.Client.CodeGeneration.CodeCustomization, Microsoft.Xrm.Client.CodeGeneration"
pause
An example for generating optionsets
CrmSvcUtil.exe ^
/codewriterfilter:"Microsoft.Crm.Sdk.Samples.FilteringService, GeneratePicklistEnums" ^
/codecustomization:"Microsoft.Crm.Sdk.Samples.CodeCustomizationService, GeneratePicklistEnums" ^
/namingservice:"Microsoft.Crm.Sdk.Samples.NamingService, GeneratePicklistEnums" ^
/url:http://servername/orgname/XRMServices/2011/Organization.svc ^
/out:OptionSets.cs
pause
* Copied from Crm 2011 sdk
To use the generated code you need using the following assemblies.
//For the on-premises or Internet-Facing Deployment (IFD) versions of Microsoft Dynamics CRM, //browse to the SDK\Bin\ folder.
Microsoft.Crm.Sdk.Proxy.dll
//For Microsoft Dynamics CRM for Outlook Online, browse to the SDK\Bin\Online\ folder.
Microsoft.Xrm.Sdk.dll
CodeGeneration extension VS no extension
Developer Extensions for Microsoft Dynamics CRM 2011 provides an extension to the CrmSvcUtil.exe command-line tool, called the Microsoft.Xrm.Client.CodeGeneration extension, which you can use to generate the data context and data transfer object classes for your Microsoft Dynamics CRM organization.
So what is the difference between use the extension or not?
As you can see from the screen dump below. When the codeCustomization extension is used, event related code is NOT generated therefore less code is generated. So use Microsoft.Xrm.Client.CodeGeneration to generate early bound crm entities are favorable. Just remember to run the bat file in the sdk\bin folder otherwise you may get error due to missing libraries.
CrmSvcUtil.exe /url:http://
/out:
/namespace:
An example for generating early bound entities with a service context
CrmSvcUtil.exe ^
/url:http://localhost:5555/Crm2011RTM/XRMServices/2011/Organization.svc ^
/out:Xrm.cs ^
/language:CS ^
/domain:playground ^
/username:user-defined-usrname ^
/password:user-defined-pwd ^
/namespace:Xrm ^
/servicecontextname:XrmServiceContext
::The following para will only work if you run this bat file in the sdk\bin folder due to required dlls.
::/codeCustomization:"Microsoft.Xrm.Client.CodeGeneration.CodeCustomization, Microsoft.Xrm.Client.CodeGeneration"
pause
An example for generating optionsets
CrmSvcUtil.exe ^
/codewriterfilter:"Microsoft.Crm.Sdk.Samples.FilteringService, GeneratePicklistEnums" ^
/codecustomization:"Microsoft.Crm.Sdk.Samples.CodeCustomizationService, GeneratePicklistEnums" ^
/namingservice:"Microsoft.Crm.Sdk.Samples.NamingService, GeneratePicklistEnums" ^
/url:http://servername/orgname/XRMServices/2011/Organization.svc ^
/out:OptionSets.cs
pause
* Copied from Crm 2011 sdk
To use the generated code you need using the following assemblies.
//For the on-premises or Internet-Facing Deployment (IFD) versions of Microsoft Dynamics CRM, //browse to the SDK\Bin\ folder.
Microsoft.Crm.Sdk.Proxy.dll
//For Microsoft Dynamics CRM for Outlook Online, browse to the SDK\Bin\Online\ folder.
Microsoft.Xrm.Sdk.dll
CodeGeneration extension VS no extension
Developer Extensions for Microsoft Dynamics CRM 2011 provides an extension to the CrmSvcUtil.exe command-line tool, called the Microsoft.Xrm.Client.CodeGeneration extension, which you can use to generate the data context and data transfer object classes for your Microsoft Dynamics CRM organization.
So what is the difference between use the extension or not?
As you can see from the screen dump below. When the codeCustomization extension is used, event related code is NOT generated therefore less code is generated. So use Microsoft.Xrm.Client.CodeGeneration to generate early bound crm entities are favorable. Just remember to run the bat file in the sdk\bin folder otherwise you may get error due to missing libraries.
Thursday, 12 January 2012
KeyType:CrmWRPCTokenKey, Expired:True. The key specified to compute a hash value is expired, only active keys are valid.
Ever accessed Microsoft Dynamics CRM and got the error “The key specified to compute a hash value is expired, only active keys are valid.” The error logged in the trace is as follows:
MSCRM Error Report:
--------------------------------------------------------------------------------------------------------
Error: Exception of type 'System.Web.HttpUnhandledException' was thrown.
Error Number: 0x8004A106
Error Message: The key specified to compute a hash value is expired, only active keys are valid. Expired Key : CrmKey(Id:d0879dd3-7f9d-de11-a5c4-0003ff392bd3, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmWRPCTokenKey, Expired:True, ValidOn:09/09/2009 20:32:01, ExpiresOn:10/12/2009 20:31:55, CreatedOn:09/09/2009 20:32:01, CreatedBy:NT AUTHORITY\NETWORK SERVICE.
Error Details: The key specified to compute a hash value is expired, only active keys are valid. Expired Key : CrmKey(Id:d0879dd3-7f9d-de11-a5c4-0003ff392bd3, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmWRPCTokenKey, Expired:True, ValidOn:09/09/2009 20:32:01, ExpiresOn:10/12/2009 20:31:55, CreatedOn:09/09/2009 20:32:01, CreatedBy:NT AUTHORITY\NETWORK SERVICE.
Source File: Not available
Line Number: Not available
Request URL: http://localhost/Contoso/loader.aspx
Stack Trace Info: [CrmException: The key specified to compute a hash value is expired, only active keys are valid. Expired Key : CrmKey(Id:d0879dd3-7f9d-de11-a5c4-0003ff392bd3, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmWRPCTokenKey, Expired:True, ValidOn:09/09/2009 20:32:01, ExpiresOn:10/12/2009 20:31:55, CreatedOn:09/09/2009 20:32:01, CreatedBy:NT AUTHORITY\NETWORK SERVICE.]
at Microsoft.Crm.CrmKeyService.ComputeHash(CrmKey key, Guid scaleGroupId, HashParameterBase[] parameters)
at Microsoft.Crm.CrmKeyService.ComputeHash(CrmKey key, HashParameterBase[] parameters)
at Microsoft.Crm.Application.Security.WRPCContext..ctor()
at Microsoft.Crm.Application.Controls.AppPage.ValidateWrpcContext()
at Microsoft.Crm.Application.Controls.AppPage.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
[HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown.]
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.contoso_loader_aspx.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Simply restart the asynchronous service and reset IIS. This should make it work!!!
MSCRM Error Report:
--------------------------------------------------------------------------------------------------------
Error: Exception of type 'System.Web.HttpUnhandledException' was thrown.
Error Number: 0x8004A106
Error Message: The key specified to compute a hash value is expired, only active keys are valid. Expired Key : CrmKey(Id:d0879dd3-7f9d-de11-a5c4-0003ff392bd3, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmWRPCTokenKey, Expired:True, ValidOn:09/09/2009 20:32:01, ExpiresOn:10/12/2009 20:31:55, CreatedOn:09/09/2009 20:32:01, CreatedBy:NT AUTHORITY\NETWORK SERVICE.
Error Details: The key specified to compute a hash value is expired, only active keys are valid. Expired Key : CrmKey(Id:d0879dd3-7f9d-de11-a5c4-0003ff392bd3, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmWRPCTokenKey, Expired:True, ValidOn:09/09/2009 20:32:01, ExpiresOn:10/12/2009 20:31:55, CreatedOn:09/09/2009 20:32:01, CreatedBy:NT AUTHORITY\NETWORK SERVICE.
Source File: Not available
Line Number: Not available
Request URL: http://localhost/Contoso/loader.aspx
Stack Trace Info: [CrmException: The key specified to compute a hash value is expired, only active keys are valid. Expired Key : CrmKey(Id:d0879dd3-7f9d-de11-a5c4-0003ff392bd3, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmWRPCTokenKey, Expired:True, ValidOn:09/09/2009 20:32:01, ExpiresOn:10/12/2009 20:31:55, CreatedOn:09/09/2009 20:32:01, CreatedBy:NT AUTHORITY\NETWORK SERVICE.]
at Microsoft.Crm.CrmKeyService.ComputeHash(CrmKey key, Guid scaleGroupId, HashParameterBase[] parameters)
at Microsoft.Crm.CrmKeyService.ComputeHash(CrmKey key, HashParameterBase[] parameters)
at Microsoft.Crm.Application.Security.WRPCContext..ctor()
at Microsoft.Crm.Application.Controls.AppPage.ValidateWrpcContext()
at Microsoft.Crm.Application.Controls.AppPage.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
[HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown.]
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.contoso_loader_aspx.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Simply restart the asynchronous service and reset IIS. This should make it work!!!
Tuesday, 10 January 2012
Dump the Entity Metadata Crm 2011
This sample shows how to use the MetadataService Web Service. It creates an XML file that provides a snapshot of attributes for a single entity using the Metadata APIs. You can then open this file with Microsoft Office Excel.
This sample code can be found in the following files in the SDK download:
Server\HowTo\CS\Metadata\HowToMetadata.cs
Server\HowTo\VB\Metadata\HowToMetadata.vb
This sample code can be found in the following files in the SDK download:
Server\HowTo\CS\Metadata\HowToMetadata.cs
Server\HowTo\VB\Metadata\HowToMetadata.vb
Changing the custom entity prefix in Microsoft Dynamics CRM 2011
The prefix that will be used when new attributes are created can be changed by updating the default publisher. This can be done by following the steps below:
1. Navigate to Settings > Customizations > Publishers.
2. Select the default publisher from the list.
3. Modify the prefix, changing it from new to the desired custom prefix, and click Save and Close.
4. Publish customizations by going to Settings > Solutions, and clicking Publish All Customizations.
Additionally, if you would like to create some fields with the new_ prefix, and some fields with the custom prefix, you can create a custom solutions that utilizes the new prefix. You can also utilize multiple different custom prefixes by creating separate solutions that utilize these prefixes.
http://support.microsoft.com/kb/2500602
1. Navigate to Settings > Customizations > Publishers.
2. Select the default publisher from the list.
3. Modify the prefix, changing it from new to the desired custom prefix, and click Save and Close.
4. Publish customizations by going to Settings > Solutions, and clicking Publish All Customizations.
Additionally, if you would like to create some fields with the new_ prefix, and some fields with the custom prefix, you can create a custom solutions that utilizes the new prefix. You can also utilize multiple different custom prefixes by creating separate solutions that utilize these prefixes.
http://support.microsoft.com/kb/2500602
Friday, 2 December 2011
Sunday, 13 November 2011
Resolving "Error: Subreport Could Not Be Displayed" in Crm 2011
The error I got:
Steps I went through to fix the problem:
1: Upload the parent report as well as the sub report
2: Make the parent report property is defined sub report edit form
Steps I went through to fix the problem:
1: Upload the parent report as well as the sub report
2: Make the parent report property is defined sub report edit form
Database Mirroring
Configure a Microsoft Dynamics CRM organization for database mirroring
Three principle components:
MSCRM_Primary
MSCRM_Mirror
MSCRM_Witness
Database mirroring overview
Three principle components:
MSCRM_Primary
MSCRM_Mirror
MSCRM_Witness
Database mirroring overview
Tuesday, 8 November 2011
Crm 2011 XSDValidation Error when importing customization.
Crm 2011 XSDValidation Error when importing customization.
Original error message:
The import file is invalid. XSD validation failed with the following error: 'The 'dateformat' attribute is not declared.'. The validation failed at: '...utoMode="VariableCount"
The issue is that the dateformat attribute is used in the customization.xml file but it is not defined in the schema.
The FIX:
Remove the dateformat attribute from the customization.xml.
Note: importing may take a while
Other things to try when the customization failed.
* Import a partial customization
* Remove the managed solutions and try again.
Original error message:
The import file is invalid. XSD validation failed with the following error: 'The 'dateformat' attribute is not declared.'. The validation failed at: '...utoMode="VariableCount"
The issue is that the dateformat attribute is used in the customization.xml file but it is not defined in the schema.
The FIX:
Remove the dateformat attribute from the customization.xml.
Note: importing may take a while
Other things to try when the customization failed.
* Import a partial customization
* Remove the managed solutions and try again.
Monday, 7 November 2011
Crm security privileges Append, Append to, Assign
Append - To control the lookup fields of the other entities on the form of this entity
Append to - To control the lookup field of this entity on the forms of other entities
Assign - To control the Owner field of this entity.
Here is a good reference for this topic. http://community.dynamics.com/product/crm/crmtechnical/b/crminogic/archive/2010/05/03/append-v-47-s-append-to.aspx
Append to - To control the lookup field of this entity on the forms of other entities
Assign - To control the Owner field of this entity.
Here is a good reference for this topic. http://community.dynamics.com/product/crm/crmtechnical/b/crminogic/archive/2010/05/03/append-v-47-s-append-to.aspx
Tuesday, 1 November 2011
The import file is too large to upload - Crm customization import error
Have fine fix for Crm 2011 but I am trying the Crm 4 equivalent.
http://support.microsoft.com/kb/918609
Monday, 31 October 2011
Sunday, 30 October 2011
Microsoft Dynamics CRM 2011 User’s and Administrator’s Guides
http://blogs.msdn.com/b/crm/archive/2011/08/16/microsoft-dynamics-crm-2011-user-s-and-administrator-s-guides.aspx
CRM 2011 Update Rollup release build numbers, and how to find them
Version Release Date Build Number KB Article
Release Candidate 5.0.9688.53 2461082
Beta (On Premise) 5.0.9585.106
Beta (Online) 5.0.9585.107
RTM February 16, 2011 5.0.9688.583 Download RTM
Update Rollup 1 April 7, 2011 5.0.9688.1045 2466084
Update Rollup 2 June 2, 2011 5.0.9688.1155 2466086
Update Rollup 3 July 28, 2011 5.0.9688.1244 2547347
Update Rollup 4 September 9, 2011 5.0.9688.1450 2556167
Update Rollup 5 October 20, 2011 05.00.9688.1533 2567454
Update Rollup 6 January 12, 2012 5.0.9689.1985
Release Candidate 5.0.9688.53 2461082
Beta (On Premise) 5.0.9585.106
Beta (Online) 5.0.9585.107
RTM February 16, 2011 5.0.9688.583 Download RTM
Update Rollup 1 April 7, 2011 5.0.9688.1045 2466084
Update Rollup 2 June 2, 2011 5.0.9688.1155 2466086
Update Rollup 3 July 28, 2011 5.0.9688.1244 2547347
Update Rollup 4 September 9, 2011 5.0.9688.1450 2556167
Update Rollup 5 October 20, 2011 05.00.9688.1533 2567454
Update Rollup 6 January 12, 2012 5.0.9689.1985
Saturday, 29 October 2011
Crm 2011 Report Extensions installation - SrsDataConnector
In short, Crm 2011 Report extension (SrsDataConnector) is required component but it is not installed as the main crm installation. You can find the detailed installation guide in the chapter 2 (Page 13) of the Microsoft Dynamics CRM 2011 Installation Guide.doc
All installations now require the CRM 2011 Report Extensions to be installed and configured on the SQL Reporting Server. If it is not installed, certain features will not work properly: reporting will not function, creating new organizations, and organization imports will be blocked until the extensions are installed and configured.
http://blogs.msdn.com/b/crminthefield/archive/2011/03/11/crm-2011-server-setup-commonly-asked-questions.aspx
http://yellowduckguy.wordpress.com/2011/06/01/microsoft-dynamics-crm-2011-reporting-extensions-is-not-installed/
All installations now require the CRM 2011 Report Extensions to be installed and configured on the SQL Reporting Server. If it is not installed, certain features will not work properly: reporting will not function, creating new organizations, and organization imports will be blocked until the extensions are installed and configured.
http://blogs.msdn.com/b/crminthefield/archive/2011/03/11/crm-2011-server-setup-commonly-asked-questions.aspx
http://yellowduckguy.wordpress.com/2011/06/01/microsoft-dynamics-crm-2011-reporting-extensions-is-not-installed/
Thursday, 27 October 2011
Crm 2011 IFD deployment. Internet Facing Deployment
There is a good MSDN blog article at the address below which I’m going to mention here for your reference (and mine for the future).
http://blogs.msdn.com/b/crm/archive/2011/01/13/configuring-ifd-with-microsoft-dynamics-crm-2011.aspx
The video
http://www.youtube.com/watch?v=ZD5qaa-G99E
Some key points
Components required for setting up Crm IFD deployment.
* Installing AD FS 2.0. AD FS has to be installed on the default website
* Configuring the AD FS 2.0 federation server
* Microsoft Dynamics CRM Server 2011 must be running on a Web site that has been configured to use Secure Sockets Layer (SSL).
* Managing certificates
* Configuring Dynamics CRM 2011 for claims-based authentication and IFD
* Creating the relying party trust for CRM and configuring the claims rules on AD FS 2.0
Windows Authentication
Claims-based authentication: internal access
Claims-based authentication: external access
http://blogs.msdn.com/b/crm/archive/2011/01/13/configuring-ifd-with-microsoft-dynamics-crm-2011.aspx
The video
http://www.youtube.com/watch?v=ZD5qaa-G99E
Some key points
Components required for setting up Crm IFD deployment.
* Installing AD FS 2.0. AD FS has to be installed on the default website
* Configuring the AD FS 2.0 federation server
* Microsoft Dynamics CRM Server 2011 must be running on a Web site that has been configured to use Secure Sockets Layer (SSL).
* Managing certificates
* Configuring Dynamics CRM 2011 for claims-based authentication and IFD
* Creating the relying party trust for CRM and configuring the claims rules on AD FS 2.0
Windows Authentication
Claims-based authentication: internal access
Claims-based authentication: external access
Subscribe to:
Posts (Atom)