Error when defaulting field value using paramaters on form

Seems to be a bug in CRM 2013 Online RU1 that generic error occurs when defaulting a lookup field value using parameters on form.

I had the following code:

       var parameters = {};      
       parameters["new_customid"] = "621E9F4C-AD5C-E311-84F4-D89D67768C0C";      
       parameters["new_customidname"] = "Record Name";
       parameters["new_customidtype"] = "new_customentity";
       Xrm.Utility.openEntityForm("new_anotherentity", null, parameters);

to pre-populate the 'new_customid' lookup field but generic error occurred.

Searched on the web for a bit and found Form Query String Parameter Tool, and noticed that the last parameter ["new_customidtype"] is not required. However, CRM SDK states that this last parameter is required.

Nonetheless, removed the last parameter and it works now.

Comments

Post a Comment

Popular posts from this blog

Request not supported new_xxx when calling Custom Action via WebApi

Image
Using CRM 2016 Online, you can create custom Action to execute custom business logic to meet your specific business requirements leveraging the workflow-like configuration window to define the business logic rather having it written in the code. The custom Action can be called via CRM WebApi, and I encountered the following error whilst working on one of the projects. 'Request not supported new_xxx' Whilst there could be different causes to the error, one that occurred in my case is because the Unique Name has been changed after it was created. The initial name was too long, hence, shortened afterwards. However, the new name is not re-generated in the API metadata. Rather than re-creating the custom API, you can find the original name before it was updated by inspecting the API metadata which you can view at the following Url. https://[organization uri]/api/data/v8.0/$metadata   Simply download the file and open in a text editor, you can search for the custom Act
Read more

Error in workflow sending email: "You cannot send email as the selected user."

Image
I have a workflow which sends notification email from a dedicated CRM account, eg. email reminder when a contract is reaching its expiry date. The following error occurred when executing the workflow: "You cannot send email as the selected user. The selected user has not allowed this or you do not have sufficient privileges to do so." To resolve the error, there are two things to check: a. The dedicated CRM account must allow other users to send email on its behalf. Login to CRM webclient as the user, Go to Options -> Email tab, then tick the option 'Allow other Microsoft Dynamics CRM users to send email on your behalf.' b. Any other users executing the workflow must be given the privilege to send email on behalf of other user. Go to Security Role, under Business Management, tick the 'Send Email on behalf of other user'.  However, I feel reluctant to allow most, if not all, users the ability to send email on behalf of other users as it
Read more

CRM 4: Cannot login - 'Invalid Action', key has expired.

Just started our development environment and added a new organisation. When I start CRM on web client, an error message displayed 'Invalid Action'. Checked the Event Log and found the following error message: Event Type: Error Event Source: MSCRMKeyGenerator Event Category: None Event ID: 18949 Date: 12/12/2008 Time: 3:50:28 PM User: N/A Computer: DEVSERVER Description:Current active key (KeyType : CrmWRPCTokenKey) is expired. This can indicate that a key is not being regenerated properly. Current Active Key : CrmKey(Id:003e7d3c-72ac-dd11-a929-0003ffce439d, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmWRPCTokenKey, Expired:True, ValidOn:11/07/2008 02:17:34, ExpiresOn:12/10/2008 02:17:34, CreatedOn:11/07/2008 02:17:34, CreatedBy:NT AUTHORITY\NETWORK SERVICE. Key Setting : For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp . Thanks to the following post, it solved my problem instantly. http://www.henrycordes.nl/po
Read more