Not able to publish or delete attribute in CRM 4.0

-
Recently I faced a problem, when I was not able to publish the entity. There were no missing fields or missing relationships. After a long troubleshooting, I found that it is happening due to currupt FormXML in OrganizationUI table for the entity. FormXML is stored in this table for entities. I had a problem with quote entity. I found out that there two entries for quote entity. It seems that one is for form opened for customization and the other for normal record rendering. there was problem with formXML for customized form.
I interchanged the flag for isCustomization of these two entries. After that, entity got published successfully. It seems entry for normal record rendering was not corrupt. So when it became formXML for customized form, it got published successfully.


Please note that this is totally unsupported way. You should take all necessary backups if you want to do this.

Comments

  1. UnknownJuly 1, 2015 at 2:47 AM

    Thank you for providing such a good data of the consumer as it is working good and also getting good and positive response for us and also we are expecting more data and we are looking forward for that ....which helps us in providing the good service
    Microsoft Dynamics AX Training | Microsoft Dynamics CRM Online Training

    ReplyDelete
  2. AnonymousAugust 13, 2015 at 11:17 PM

    Amazing Blog created by you.It is really informative and helpful for me.
    Colocation Hosting in pune, Zimbra Hosting in pune,virtual private network in pune, Certified Datacenter in pune, network Infrastructure Solution in pune

    ReplyDelete
  3. Parul PathakMay 22, 2021 at 4:39 AM

    This site helps to clear your all query. rajasthan university bcom final year result 2021
    uniraj ba 3rd year result 2021 This is really worth reading. nice informative article.

    ReplyDelete

Post a Comment

Popular posts from this blog

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-000000000
Read more

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