Tag: CRM

Building URL to the CRM record that triggers the workflow.


Hi,

I was just looking for the various options for the above scenario.

These are the different options that i found

http://www.dynamicscrmtrickbag.com/2009/09/13/email-record-links/

http://www.powerobjects.com/blog/2009/02/23/crm-40-links-in-workflow-emails-part-2/

http://blog.powerobjects.com/2008/09/16/crm-40-links-to-entities-in-workflow-email/

http://a33ik.blogspot.com/2009/06/creation-of-shortcut-to-record-in.html

and finally using ‘Url Functions’ extensions found in

Business Productivity Workflow Tools

find more information on it over here

http://blog.customereffective.com/blog/2009/10/make-microsoft-dynamics-crm-workflow-more-useful.html

Bye.

Passing parameters to NavBarItem’s url property in CRM.


For passing custom attribute values as parameter to the navBarItem on an Entity, we could use the following similar JavaScript

 

// get the id of navbaritem using IE Dev tool

var navBarItem = document.all.navBarItemID;

// get the value of the field to pass as parameter

var fname=crmForm.all.firstname.DataValue;

// if it is not null than attach a function that uses openIsvWin function of CRM

// there you could pass your parameters for the url

if (navBarItem != null) {

navBarItem .onclick = function() {

openIsvWin(‘http://localhost/default.aspx?fname=’+fname, false, -1, ”);

}

}

http://www.eggheadcafe.com/software/aspnet/29468928/navbaritem-url-property.aspx

 

Bye..

“Insert failed for entity ‘TimeZoneLocalizedName’, batchRows=1144 with exception System.Data.SqlClient.SqlException: Cannot bulk load because the file "C:\Documents and Settings\\Application Data\Microsoft\MSCRM\BCP\.bcp" could not be opened” in Data Migration Manager


I got this error in data migration manager at the synchronizing stage.

While searching for it I found that this error occurs in case if we have installed Data Migration Manager on the CRM Server and have selected the SQL Server on a remote machine as database.

The error got resolved on re installing the Data Migration Manager with SQL Express.

Bye..

“The path is not of a legal form” error while installing Microsoft Data Migration Manager.


This error occurs while installing Data Migration Manager on CRM server.

To resolve this error we need to modify the following registry settings

Key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
CurrentVersion\Installer\UserData\S-1-5-18\Products
59DD8CB00184F24E99A62CF4D6109FA\InstallProperties]

Value: InstallLocation

Set the value to C:\Program Files\Microsoft Dynamics CRM 
The installation would run without error after this.
Bye..

Opening Microsoft Dynamics CRM in Chrome browser.


Using IE tab extension released for Google Chrome we could open our MS CRM inside Chrome.

IE tab extensions https://chrome.google.com/extensions/detail/hehijbfgiekmjfkfjpbkbammjbdenadd

chromeMSCrm

Bye..

SoapException:Server was unable to process request on Update using CrmService.


Hi,

We were receiving the above error on running a custom aspx page.

This page was configured to be called on click of an ISV.config button from an entity’s form.

The page was using CrmService web service to update the entity on which it was being called.

On checking the stack trace, we found that error was coming from within this function of the page

CrmService crmService = new CrmService();
crmService.Url = //web service url
crmService.Credentials = System.Net.CredentialCache.DefaultCredentials;

salesorder salesOrder = new salesorder();
salesOrder.new_issuer = userName;

salesOrder.salesorderid = new Key();
salesOrder.salesorderid.Value = new Guid(poID);

crmService.Update(salesOrder);
There was nothing in the code that could have resulted in the above error as correct guid of the record was getting passed.
After a little more investigation we finally realized that the issue was with a post update callout. The post update callout was the one which was throwing the error.
And as we were updating the record using a custom page, the callout was also getting fired. So finally we corrected the post update callout and the custom page also started working fine.
Bye.