MS CRM 4.0 Worflow Issue

-
Recently I came across a scenario where it was required that workflow be triggered on change of a read only only field.

While testing I found that the workflow wasn't getting fired. I added the code to ForceSubmit the field OnSave of record.
Even after that the workflow didnt execute on change of that field.

Ultimately, I had to enable that field so that the workflow could trigger on field change. Additional logic (simply a workaround) had to be applied in order to achieve the desired functionality.

Comments

Post a Comment

Popular posts from this blog

IFD Implementation for custom web pages and Anonymous Access

-
When deploying my custom web pages for an IFD deployment, I got a FileLoadException (Exception from HRESULT: 0x80131401) on accessing the page in the browser. Basically, this issue arose since anonymous access was somehow disabled for the “ISV/CustomPages” application in IIS while by default it is enabled for the Microsoft Dynamics CRM website. This implied that my custom web site was using Windows NT Authentication, while the Microsoft Dynamics CRM Website was enabled for anonymous access. Hence, I got “Loading this assembly would produce a different grant set from other instances” on accessing any of my web pages from within MS CRM. Simply turning on anonymous access for my custom website did the trick and rendered all my custom web pages correctly :)
Read more

Using CRM Services to create or update records in large numbers

-
Recently, I implemented a plug in code which invoked auto creation of records from a contacts list (rather marketing lists based on MS CRM contacts) for my custom entity. The code worked well but it hanged whenever I considered a marketing list of more than 3000 contacts. The error logged read: Only one usage of each socket address (protocol/network address/port) is normally permitted. Basically, the error was thrown when the creation process exhausted the limit of socket connections allowed by the IIS and the SDK still polled for another connection and consequentially timed out after a certain number of records were created. A quick workaround for this is to change the following entries in the registry: HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort to 65534AndHKLM\System\CurrentControlSet\Services\Tcpip\Parameters\TCPTimedWaitDelay to be 30 The link : http://dmcrm.blogspot.com/2008/07/updating-records-in-mass-via-sdk.html also mentions a resolution of this by us...
Read more

Issues after Re-Naming MS CRM Servers computer/machine name

-
Currently I faced a scenario where the machine on which MS CRM 4.0 was installed was required to be renamed on LAN. My deployment had the SQL Server installed on another machine on LAN. After changing the MSCRM Server machine name, MS CRM browser stopped working and started showing error “SqlException: Login failed for user [Domain Name]\[New Machine Name] .” This error comes when the MS CRM server related entries in registry and database (that refer to the server name) have not yet been changed to the new server name This problem could be solved by 'Repairing’ the MS CRM 4.0 installation on the machine after renaming it. Go to the Control Panel -> Add or Remove programs-> Microsoft Dynamics CRM Server. Repair the installation. Repair installation internally performs the following actions: a. In the registry, ServerURL key value at HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MSCRM is updated with the new machine name (example: the value would be like “http:// :5555/MSCRMServices”...
Read more