Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Remove hard-coded behaviour when using lookup classes
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Expand all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Michael Hoehne  
View profile  
(1 user)  More options Apr 10 2006, 8:33 am
Newsgroups: microsoft.public.crm.developer
From: Michael Hoehne <michael.hoe...@nospam.nospam>
Date: Mon, 10 Apr 2006 05:33:01 -0700
Local: Mon, Apr 10 2006 8:33 am
Subject: Remove hard-coded behaviour when using lookup classes
In CRM 3.0 we're currently unable to modify the items displayed in a lookup
window. I looked into the JavaScript implementation and thought that we
should be able to provide custom lookup filters through adding a new xml file
in the <program files>\Microsoft CRM\Server\ApplicationFiles folder. However
specifying a *new* lookup class always leads to a FileNotFoundException. I
finally had a look at the CRM assemblies and found that this is hard-coded in
the GetLookupXml function (I'm not going into more detail here).

Without this restriction we could use the following very simple addition in
an onLoad event of a CRM form:

var oLookup = crmForm.all.primarycontactid;
oLookup.lookupclass="stunnware_MyAccountView";
oLookup.AddParam("stunnware_accountid", crmForm.ObjectId);

This overwrites the standard lookup class and adds an additional parameter
to only display the contacts associated with the current account. The only
thing needed to make this working is to remove the hard-coded behaviour
comparing against a list of 69 predefined lookup classes. It won't break any
functionality but would allow us to easily modify the displayed items in the
lookup dialog.

Ideally, we will find the lookupclass and maybe the parameters in the form
designer and/or the attribute defintiion, whatever makes more sense.

Thanks
Michael
--
http://www.stunnware.com/crm

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/Businesssolutions/Community/NewsGroups/dgbro...


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google