Friday, March 4, 2011
Adding bookmarks to your CRM form.
In my current implementation, instead of adding many tabs to the CRM form, we ended up adding multiple sections on one tab.
The end result was that the form became extremely long and it was getting only longer. So, in order to enhance the user experience, there was a need to add a bookmark style facility to the page.
The end result was that the form became extremely long and it was getting only longer. So, in order to enhance the user experience, there was a need to add a bookmark style facility to the page.
After a lot of thought I went ahead and asked for some ideas in the CRM newsgroups. I got some great ideas from the community and it turned out that implementing this functionality was simpler than I had imagined.
So, I created one HTML page with links to the various sections(section1, section 2 etc.). When the user clicks on any section link, I will simply set the focus to the first field on that section, there by redirecting the user to that section.
Simple, isn’t it? 

Labels:
Dynamics CRM 4.0
Simple Filtered Lookup based on Picklist Values
I had a parent entity containing records classified into 2 different disease categories ('Diabetes' and 'Cholestrol').
In my related entity, there was a picklist which had the above 2 disease categories. The criteria was that when the user selected a particular disease cateogry in the picklist, the parent entity lookup should show as a pop-up showing only the corresponding disease category records.
Ex: If the user selects ‘Diabetes’ in the picklist, then the lookup should pop-up showing only records of type ‘Diabetes’. After some searching, I found this blog:http://advantageworks.blogspot.com/2008/02/pseudo-filtered-lookup-dialog-in.html, which was describing a similar scenario. Here is how I implemented this:
1. I went into customizations and opened my parent entity.
2. Then I clicked on “Forms and views” and opened the lookup view.
3. Then I clicked on “Add Find Columns” and selected “Disease Category” column.
4. Saved and Published the entity
5. Next, I opened my related entity’s form.
6. In the onchange event of my picklist, I wrote the following code:
2. Then I clicked on “Forms and views” and opened the lookup view.
3. Then I clicked on “Add Find Columns” and selected “Disease Category” column.
4. Saved and Published the entity
5. Next, I opened my related entity’s form.
6. In the onchange event of my picklist, I wrote the following code:
if(crmForm.all.new_Picklist.SelectedText=="Diabetes") { var criteria= 'Diabetes'; crmForm.all.new_parentLookupId.additionalparams = 'search=' + criteria; crmForm.all.new_parentLookupId.click(); // Launch the parent lookup as a popup. }7. Save and publish the related entity. So, basically this is the same as opening the lookup and typing ‘Diabetes’ in the search box of the lookup. It’s not filtered in a strict sense.
–Srihari.
Labels:
Dynamics CRM 4.0,
Javascript
Accessing ASP.NET controls within an IFRAME in CRM 4.0
There was a requirement to disable an drop-down list which was in an IFRAME in a CRM form.
The below code allowed me to access the value of the ASP.NET drop-down list:
document.frames.IFRAME_Test.document.all.DropDownList1.value;and the below code allowed me to disable it:
document.frames.IFRAME_Test.document.all.DropDownList1.disabled= true;
Labels:
Javascript
Adding Syntax Highlighting to Blogger
A very detailed and great explanation has been provided by Matt Boll at his blog:
http://heisencoder.net/2009/01/adding-syntax-highlighting-to-blogger.html
http://heisencoder.net/2009/01/adding-syntax-highlighting-to-blogger.html
Labels:
Useful links
Failure: contact_activity_parties: Cascade link type ‘NoCascade’ is invalid for Delete
I was trying to import a contact entity into one of my CRM instances today and I was getting the strange error “Failure: contact_activity_parties: Cascade link type ‘NoCascade’ is invalid for Delete”.
Luckily I managed to find this thread http://social.microsoft.com/Forums/en/crmdeployment/thread/c2292223-6d76-4c77-919a-99effa077bc7 where one of the users was having the same problem. I tried out one of the suggestions posted by the user.
Apparently this is caused because of some issues with the relationship structure in the customization file. So, I opened the customiation.xml file and I searched for “contact_activity_parties”.
Sure enough, there was a relationship defined
OneToMany ActivityParty Contact partyid
–Srihari.
Labels:
Dynamics CRM 4.0
Wednesday, January 17, 2007
Subscribe to:
Posts (Atom)