Salesforce IdeaExchange
- then -
Customization Comments
| Customization Ideas
|
User Experience Comments
| User Experience Ideas
|
Force.com Platform Comments
| Force.com Platform Ideas
|
Search and Navigation Comments
| Search and Navigation Ideas
|
PerGeert 10/16/06 |
Another example: When I e.g. on the Contact Edit Tab click the magnifying glass on the Reports To field, all contacts are listed in the Lookup Dialog. That is somewhat cumbersome when I have thousinds of contacts and only am interested in contacts from the same account as the originating contact. When I search on Products on OpportunityProductLine, all active products within the price list is displayed. Based upon fields on the opportunity I am in many cases able to limit the list. |
|
jgreene 10/18/06 |
Someone posted a new idea that looks like a duplicate of this. http://ideas.salesforce.com/article/show/25930< dupes! |
|
Andrew_Smith 10/19/06 |
The dup is gone. See below for chain of comments on it... A_Smith: I wanted to expand on this a little. Some customers want filtered lookups with a static filter (maybe only open cases or closed opportunities) that applies across the board. Others want a context sensitive filter such as only contacts on a particular account when creating contact roles. If you like this idea, please promote it and add your comments... jgreene: Here's my use case, which is similar to Johnny_Q's except I think the relationship lookups go one level "deeper." My company sells hardware called an "appliance." An account can have one or more "installations," and each installation can have one or more "appliances." On the cases object, I've added a lookup field that links to the "appliance" object. That's so that for each case, we know which appliance it is associated with. When I create a case and click the "appliance" lookup button, I want the default list that appears to be filtered in this manner: I only want to see appliances which are members of installations which belong to the case's account. However, sometimes there are exceptions so I don't want my input to be *limited* by this filter. I want to be able to type an arbitrary appliance ID into the lookup box and save it. Johnny_Q: We linked assets to contracts with a link object. When I add assets to the contract I get a list of all assets instead of the assets belonging to to linked account |
|
5WheelSteve 10/19/06 |
This is a feature we definitely need to control extra-long picklists. I want to implement an inhouse version of campaigns. We would like to be able to define campaigns and then a number of campaign assets related to each campaign. The problem is there are a few hundred campaign assets from which our sales people need to choose. The assets already have an associated "type". It would be very useful to have 2 related picklists to discern which asset needs to be added. |
|
patm 10/25/06 |
This is very standard in a support situation. When I have a case I want to relate the case to an asset. Ideally when I lookup the assets it starts with returning just the assets that are owned by the account that is related to the case. To have this generically available would be great. |
|
Vinaya 11/08/06 |
This will be very useful feature. The way we would like to use it is, on Opportunity, when I wat to add a partner to the oppty, and use the Partner related list, I would like to filter the lookup to only limited "types" of accounts - e.g. "OEM, Reseller, Distributor" etc. and avoid showing accounts who are of type "Customers". |
|
hp 11/09/06 |
In our case, we want to assign a Task to a Product. We would like the filter to limited the results by 'Product Family'. Additionally, we need multiple lookups (named lookups) to be context sensitive - at least. This will allow the filter to be dynamic based on the user who is assigned to a Product Line/Family. |
|
BWMoon 11/09/06 |
this feature would be immensely useful and has been requested by my users multiple times. mostly that if they do a lookup on a record already linked to an account that it filters the contact lookup to those contacts listed at the account only. |
|
NoSandFleasPlease 01/07/07 |
Such a feature might be useful to us, but in EE filters would have to be definable by record type, page layout, division or some other means so that users from different divisions aren't locked into one division's idea of how things should work. Ultimately, all lookups, searches, views, and reports should have the ability to select multiple parameters dynamically. |
|
Lynne 01/31/07 |
Another Use Case: On a task on an oppy, use the look up for contact, have it default in the contacts on the oppy first before overriding and manually searching. |
|
wb64wyatt 02/01/07 |
I have thousands of customers that have the same name, like Wendys, when I do a look up I get all wendys and can't filter on what in need. Can we make the lookup like advanced search or at least can we sort on all fields? |
|
Kjongberg 02/22/07 |
I am working on an application for a client at the moment and we want to be able to limit lookups to specific record types. I was going to put in a new idea when I saw this one. Is there any way of rewording the original one. I think it might be lacking promotions because it's not clear enough and doesn't contain an image... |
|
KirstenJ 02/22/07 |
I think it would be great if we could filter a lookup according to specific business rules. I can think of many situations in our current application where it would be useful to limit the lookup options for our users. For example, you might want to lookup only a particular Contact role, or Record Type. This would be extremely useful. I'm surprised it hasn't already been implemented! |
|
pludlow 02/22/07 |
My client is very keen to have this feature enabled - we are using sub typed objects where some sub types are allowed certain relationship and others aren't. we would like to enforce this through a filtered lookup, so one record sub type has one set of records in the lookup, and another has a different set. |
|
MLhp 02/26/07 |
When creating multiple opps from an activity, the contact lookup should default to the account of originating activity. |
|
CRMSuggestions 02/26/07 |
My client is very keen to have this feature enabled too, when perform campaign lookup search, would be nice to have the ability to customize the result page. |
|
ASliver 03/05/07 |
With complex sales organiztions involving suppliers, distributors, and end customers all using the account object (particularly to use PRM), there has to be a way to segment the type of account you are seeking |
|
StraightThrough 03/12/07 |
We would be able to make use of this feature if it were implemented to allow pickers to display a filtered set of data. Ie: have pickers filter by certain parameters (similar to how Workflow Rules are set up). In our case, we have the concept of "Inactive" on Contacts. For all Contact pickers, we'd like to display all Contacts where "Inactive" is "Unchecked". |
|
RikvdW 03/28/07 |
We use a custom object with a lookup to "Products". To ensure data quality, I need to be able to restrict the lookup to only "Active" products. |
|
jgreene 04/27/07 |
This is a must... the current lookup dialogs: 1) Are too slow 2) Can only match against one field 3) Would benefit greatly from the ability to filter the lookup |
|
janines 06/05/07 |
Merged Idea
originally posted 06/05/07
Filter lookup results
It would be very useful to be able to filter lookup results.
Example: an account has different types (e.g. 'customer', 'competitor'). If I want to track the main competitor for an opportunity, and add the field 'main competitor' to an opportunity with a lookup data type to 'account', it would help to able to filter the accounts to the ones of type 'competitor'. This filter could be predefined on the customization layer with the ability to override or remove it in the UI. |
|
RikvdW 06/05/07 |
Merged Comment originally posted 06/05/07 |
|
janines 06/05/07 |
Merged Comment
originally posted 06/05/07
RikvdW is right - this is a duplicate to 25614, which I did not find.
|
|
LucBaart 06/05/07 |
Merged Comment
originally posted 06/05/07
weird, I just did the same search and found it ...
|
|
RikvdW 06/05/07 |
Merged Comment
originally posted 06/05/07
seems to be a local bug or Heisenberg bug ...
|
|
Johnny_Q 06/05/07 |
Merged Idea
originally posted 10/18/06
Filtered Lookup Fields (was: Lookup fields only showing related data)
We linked assets to contracts with a link object.
When I add assets to the contract I get a list of all assets instead of the assets belonging to to linked account |
|
James_McGill 06/05/07 |
Merged Comment
originally posted 10/18/06
I wholeheartedly agree. This is a common request from users.
|
|
A_Smith 06/05/07 |
Merged Comment
originally posted 10/18/06
I wanted to expand on this a little. Some customers want filtered lookups with a static filter (maybe only open cases or closed opportunities) that applies across the board. Others want a context sensitive filter such as only contacts on a particular account when creating contact roles. If you like this idea, please promote it and add your comments...
|
|
jgreene 06/05/07 |
Merged Comment
originally posted 10/18/06
Here's my use case, which is similar to Johnny_Q's except I think the relationship lookups go one level "deeper."
My company sells hardware called an "appliance." An account can have one or more "installations," and each installation can have one or more "appliances." On the cases object, I've added a lookup field that links to the "appliance" object. That's so that for each case, we know which appliance it is associated with. When I create a case and click the "appliance" lookup button, I want the default list that appears to be filtered in this manner: I only want to see appliances which are members of installations which belong to the case's account. However, sometimes there are exceptions so I don't want my input to be *limited* by this filter. I want to be able to type an arbitrary appliance ID into the lookup box and save it. |
|
WrogWrog 07/03/07 |
I have also wanted some functionality like this for a while, but just got round to voting. I agree with A__Smith, that some context-sensitive filtering might be required, but I believe we should have static AS WELL. My rationale is, for instance we have account types which we link to various objects. We would like to filter the list of available accounts depending on the object, and ideally on the record type too - this should be defined at object level. However, for ALL lists on all objects and all record types we would like to exclude accounts we have flagged as "dead" - this should be defined on the Account object. On lookup relationships we would like to be able to filter based on any field type, including checkboxes, dates, text, formula fields etc. In fact, we'll glady accept everything you can do in this area!! |
|
FICLSalesForceAdmin 07/05/07 |
I think filtering lookups by record type is a good place to start. I can see the need to filter based on user role, but filtering based on record type is a must have. |
|
Theresakk 07/09/07 |
I promoted this. My original suggestion was: When logging a call, task, event, etc., there is a space to enter the contact name. If you select the lookup tab (either first, or if the name errors out) the lookup should be restricted to the company name that is already specified in the entry. What currently happens is that you type the name in again, searching all companies, and wasting a step. |
|
mmennen 07/09/07 |
Not sure whether to post here or on another idea, but what we really need is the ability to filter Opportunities on look-up, especially when associating an Opportunity with an email/event/task. We would like the option to make the look up pull in only Opportunities = Open, for example. Or Opportunities = Closed Filled. |
|
pkanumury 07/11/07 |
This capability would be a huge productivity win for our users as we have millions of records in certain objects and being have to have a predefineed custom filter per page layout for look up fields would make the user experiencec 100X easier, please make this happen!!! |
|
sparky 07/11/07 |
+1 for me. I'd really like to see dynamic filtering here as well. example: if I build a custom obj that is detail-master to Contacts, and also looks up to Opps, would like to be able to limit this to Opps that are associated to that same contact. Thanks! |
|
chris925 08/13/07 |
Functionality similar to the customizability of the home page search filters would be perfect... |
|
OH 08/14/07 |
Would like to restrict the Account lookup on an Opportunity to only show Accounts owned by the logged in user. |
|
asutherland 08/17/07 |
Merged Idea
originally posted 01/09/07
Customize results in Name Lookup popup windows
I have users requesting the ability to customize the default search results in the Name Lookup popup windows. For instance, when a customer service rep is creating a new activity for a case that is related to an account, it would save a lot of time if the Name Lookup box would just list the contacts for the account that is related to the case. The same holds true for activities related to Opportunities and Leads, or activities related to Accounts and Contacts. The default search results should offer the option to filter based on the relational information of the parent records if the user chooses to implement such a filter.
|
|
EmilyLiggett 08/17/07 |
Merged Comment
originally posted 01/12/07
I believe this is a duplicate.
Take a look at these: http://ideas.salesforce.com/article/show/43928 http://ideas.salesforce.com/article/show/33515 I like the idea. |
|
snowfox 08/31/07 |
Sounds like a great idea to me!! When can we expect it? |
|
TimMadigan 09/25/07 |
Great idea. We added the Opportunity to the Contracts and I would love for it to only give those opportunities linked to the required Account on the Contract. |
|
sfauser 09/25/07 |
Merged Idea
originally posted 04/26/07
Drop-down filters in the lookup dialog
It helps a lot if there are many look-up values and the user tends to work in a browse-and-pick manner. Say, when looking up an account, it would be much more friendly if a user can list all [Industry = "Pharmaceutical" and State = "AZ"] accounts and pick the one he wants.
|
|
it@mce.be 09/25/07 |
Merged Idea
originally posted 04/10/07
Lookup Functionality
It would be nice, to be able to specify a where condition in the Lookup function.
This way, we can eliminate inactive Accounts / Contacts and other values from the list |
|
dkelly 09/25/07 |
Merged Comment
originally posted 06/08/07
Duplicate to Idea # 25164 "Filter on Lookup"
http://ideas.salesforce.com/article/show/25164 |
|
rflorig1 09/25/07 |
Merged Idea
originally posted 04/05/07
Fully Customized Lookup Fields and Dialogs
Salesforce should allow the administrator to explicitly describe what kind of lookup should be executed. Rather than just a lookup to a particular object, allow there to be a lookup to a particular record type or a value from a picklist field, etc.
|
|
Magix 09/25/07 |
Merged Idea
originally posted 07/10/07
Dependent Lookup Fields
If you add two lookup fields to a record, then you should be able to make the second lookup dependent on the first lookup that was created.
For example, if you have three objects: Account, Opportunity, and Site (custom object). When the User is on the Opportunity record, then there is a lookup to the "Site". It would be nice if the sites that are displayed in the "Lookup" results are limited to the sites that are related to the Account (that the Opportunity is realted to). With current functionality, all Sites within the application are shown not just ones limited to the Account. Essentially, this should be the same as the dependent picklist functionality that is currently available. |
|
a0t300000008ZRV 09/25/07 |
Merged Comment
originally posted 07/12/07
This would be extremely useful. For each call that we enter we select the Asset that the call is related to. It would be great if the Asset lookup only displayed Assets at the Account that the Call is being created for, instead of having to search for the right Asset, and potentially choosing the wrong one.
|
|
EmilyLiggett 09/25/07 |
Merged Comment
originally posted 09/24/07
Nice idea. Here are some similar ones: http://ideas.salesforce.com/article/show/43928, http://ideas.salesforce.com/article/show/33515
|
|
lage 09/25/07 |
Merged Idea
originally posted 08/20/07
Filtering Lookup Fields by Profile/Role/Groups/etc
ex. We have a lookup field called 'Salesperson Responsible'. We don't want to show a small 30 person division all 500 users to choose from. We only want to allow them to select users from One specified profile, which includes 30 people.
Salesforce.com DESPERATELY needs to add the functionality to filter lookup fields by Profiles/Groups/Roles/etc. I can't believe that this has not been implemented yet. |
|
spunkino 10/24/07 |
Every user we have had has issues with adding a contact to a task from account view and the contact pick list NOT being restricted to contacts from the current account. Creating tasks from contact view presents a similar problem i.e. you need to know the name of the account as it is not shown on screen. This feature is needed asap. |
|
pingzing47 10/26/07 |
Like many others it would be easier to limit the Lookups to a particular type of account. For example, when in the Partner section of an opportunity, be able to filter on just accounts designated as Competitor or Partner, thus eliminating all of the other types of accounts. We are using the Partner section (we call it Competitor/Partner) to id competitors we are competing with on an Opportunity. Too many choices to find easily when presented will all records. |
|
EmilyLiggett 10/29/07 |
Take a look at the Lookups Enhancements blog post: http://blogs.salesforce.com/user_experience/2007/10/lookups-enhance.html |
|
jeepee 11/05/07 |
And another link, here very specifec details on this regarding cases and http://ideas.salesforce.com/article/show/96591 |
|
austineti 11/08/07 |
My support line needs to see only active customers not the extremely long list of prospects we have. There are many other examples of why this is needed. |
|
lage 11/24/07 |
Is there any idea when this feature might be implemented? This is one of the main things holding us back in the system and causing much customization. - Tanner Shamrock |
|
jmao09132007 11/28/07 |
Yeah I agree that without this function the look-up dialog looks like a prototype thing. |
|
SFDC_palace Jan 18 |
PLEASE PLEASE Salesforce.com add this functionality... How many promotions does it need? |
|
nanahg Jan 23 |
Gotta have this! Thanks! |
|
Omegan Jan 24 |
This would save us loads of time, and eliminate the need to have a second salesforce tab open to search for related items in an account. Also saves paper, it would no longer be necessary to write the info down before creating a new case. I like the idea of the filter being optional, since in some cases the data being looked up may not be related to the account. Without filtering in lookups, I agree with jmao above, it is very clunky. |
|
hpPMO Jan 24 |
Any update since your last post, EmilyLiggett? |
|
EmilyLiggett Jan 30 |
SusanK, who is our product manager for this feature, posted this update as a comment on my blog entry: There is a pilot program that is scheduled to begin with the Spring 08 release that will include filtering, paging, sorting and column customizations for accounts and contacts. The rest of the objects are targeted to be in pilot for the Summer 08 release. If you are interested in participating in the pilot, please contact your CSM or sales rep and ask about the Search Lookups Pilot. |
|
falkdal Feb 12 |
Changed status to Ideas Under Consideration. |
|
pruthvi Feb 20 |
Need some help on how to invoke an s-Control in the Opportunity Edit new opportunity page layout, i.e., while creating a new record there should be a provision for the user to click on a button or a link which invokes a custom s-control. |
|
pruthvi Feb 20 |
How to implement a default filter in the Lookup to products in Opportunity. Only required products should get displayed. |
|
Drawloop Mar 7 |
Another example: When re-assigning an Approver during an Approval Process, only list Administrators. Perhaps this would be based on some standard check box on a profile called Approve Objects. |
|
mike0 Apr 1 |
We went live on salesforce today, and this was comment #1 from the users. We have a hierarchy of custom objects that we set up for our needs, so we've made this shortcoming quite noticeable. Hopefully something like the existing dependent picklists (as others have noted) will become available in the near term. |
|
SusanK Apr 14 |
Changed status to Coming in Summer 08. |
|
JohanLiljegren Apr 14 |
SusanK: Seriously? Wow, I think I love you. This is such a big pain point for us from the beginning. |
|
Marc_Baizman Apr 15 |
YESSSSSSSSSSSSSSSSSSSSSSSSSSSSS |
|
AlexCRMmanager Apr 16 |
woohoo!!! finally! |
|
TrevorIDP Apr 16 |
Great news now we can scrap some of the S-Control we had in place to do this |
|
dlange@centerstance.com May 12 |
This feature doesn't appear to be in the Summer 08 Pre-Release. Anyone know when it will become GA? |
|
WrogWrog May 18 |
It IS in the pre-release in my sandbox (once I've switched everything on). HOWEVER, it doesn't do what I think everyone actually wanted. You can define a set of fields which the user can use to filter on as well as the usual search on the object name field. It does NOT allow me to do what I really really really need to do which is to specify a DEFAULT for one or more of those filters. Specifically, as described in the original text for this idea, I need to ALWAYS exclude certain records from a lookup, such as Assets which have expired, contacts which are dead, opportunities which are closed etc. So close, and yet so far from what I need as to be of no practical benefit. So, SusanK of Salesforce, I don't think you can say "Coming in Summer 08". |
|
AlexCRMmanager May 19 |
It is REALLY annoying that Salesforce keeps on hijacking our Ideas and marking them as delivered when the functionality doesn't even come close to what we've asked for. When are they going to start really listening to us? |
|
rvbdmelissa May 28 |
I agree that this feature was not delivered. I was so excited about this, but was quickly disappointed. Salesforce, I believe that the functionality evreyone was looking for is the ability to enter formula type of criteria onto custom lookup fields so that the results returned are based on that criteria. Please do not tag this feature as having been delivered. |
|
WrogWrog May 29 |
SusanK! Are you listening? |
|
TBShaff Jun 9 |
This idea should not be considered as "Delivered"!!!!! As stated above, the request is to have the ability to query records using parameters, not after the results are received!! Here is the original request: "I would like to filter lookup view to restrict records return based on some condition." SalesForce, you NEED to acknowledge the fact that you are not delivering what has been requested! put this idea back into the UNDELIVERED list, thank you! |
|
TrevorIDP Jun 11 |
I agree its NOT delivered I have been playing functionality in Sandbox and ability for users to select a filter is not what the idea is about. I would like as an Administrator to restrict lookup data avaiable to my users. I don't what them to have to select a filter. |
|
NetGenIT Jun 11 |
Unbelievable... I have been waiting for this functionality for over 2 years now. For the past 3 months, i had believed we were finally getting this functionality. It is clear from the release notes we are not! Does anyone have a custom s-control you can share to accomplish this? |
|
srinivasan_babu Jun 16 |
I hope creating profiles and providing sharing setting can over come this issue. i our company we are using three instance in one sandbox like OEM,APAC and EMEA where we use different profile and different set of records where APAC account should not be visible to other instance so we used providing access in sharing setting has over come this issue |
|
SusanK Jun 18 |
Changed status to Ideas Under Consideration. |
|
robcyborg Jun 19 |
Despite the fact it is useful, please SalesForce consider it ... just make sense. I mean every data oriented development just has to propose such a feature of displaying a list of values that are filtered based on custom criteria. Would you please create relationships between an object and a lookup list? |
|
isaha@navatargroup.com Jun 27 |
Merged Idea
originally posted Mar 26
Filterable Lookups
The lookup to objects should be filterable to provide more versatility and customization as per varied requirement.
For example for a salesforce implementation I was using record-types to form 2 versions of the same object. The object used was Account and we were using 2 record types for this viz:- 1. Institution 2. Limited Partner So far so good. But our client had the requirement wherein the lookup based on certain condition would show only record of a certain record type say "Institution". This I couldn't do using salesforce normal implementation. So I think filterable look-ups are a necessity. |
|
SusanK Jun 27 |
Merged Comment
originally posted Apr 2
This is a great idea, and we're working on a feature for this right now! Some questions:
Would you be interested in having default filter values, that the end-user doesn't ever see, but always has applied to their lookups? Would you want to be able to define different filters for different profiles? |
|
SusanK Jun 27 |
Merged Comment
originally posted Apr 2
Changed status to Ideas Under Consideration.
|
|
AlexCRMmanager Jun 27 |
Merged Comment
originally posted Apr 2
This is a duplicate of this
http://ideas.salesforce.com/article/show/25164/Filter_on_Lookup< and there are several other duplicates of this idea out there that haven't been merged yet. |
|
isaha@navatargroup.com Jun 27 |
Merged Comment
originally posted Apr 2
Thankx Susan for your remarks, please find my response as under:-
Would you be interested in having default filter values, that the end-user doesn't ever see, but always has applied to their lookups? Having default filter values which are not exposed to the user is a great idea as it would provide the programmer or implementer with lot of flexibility and control. Would you want to be able to define different filters for different profiles? That would be an added advantage Susan. Thanks a lot for your response. |
|
tanner_shamrock Jun 27 |
Merged Comment
originally posted Apr 28
I have created s-controls that act as filtered lookups. They only show the records related to the current Account (or whatever criteria is involved).
I can do customizations like this or anything else within the realm of APEX and s-controls. If anyone is interested in having customizations performed, contact me at tannershamrock@gmail.com and I'd be happy to assist for a reasonable price. |
|
agluewvrs Jun 27 |
Merged Comment
originally posted Jun 26
merge this idea with the others..
|
|
NetGenIT Jun 29 |
SusanK, We need to be able to specify a formula (or better yet SOQL query) to the Lookup field, behind the scenes so that the user doesn't need to know anything about filtering. |
|
boc Jul 19 |
Would be very very very useful. Both static and dynamic - Like NetGenIT comment that would actually be ideal, or simply utilize both as in Workflow meets "x" conditions or "y" formula is true. |
|
goforcego Jul 31 |
For my client, the need is to show only America customers in the lookup if the user is in NA. Instead of using divisions, I want to use record types. So ability to filter lookups based on record types would be very useful. |
|
scraps Aug 12 |
Love the idea. +10 Need to ensure that it works within objects as well as cross objects ie for a lookup on an account that references other accounts. This would make sure the functionality exists for our Person Account users also. |
|
dutom Aug 19 |
I dont see a need at the profile level. I see these customized lookups at the object level and leveraging page layout level. similar to how related list buttons are. They need to allow for multiple configurations, Example: A Contact pagelayout has 3 lookups to account each with a different customized lookup to account. In the pagelayout edit section you can right click on the lookup fields and configure them. criteria includes: choosing custom layout, override the defaults, add static filter... As for the customized lookups, allowing static filters (dont see) is a great option, but visible filters that you can set the defaults using cross-object formulas is a required. |
|
agluewvrs Aug 23 |
Merged Idea
originally posted Jun 5
Hard Coded Filter on Lookups
Summer 08 lets a user filter lookup results, yay!
A nice feature though would be the ability of an SFDC admin to hard code/set a filter on a particular lookup field. Use case would be an Account Lookup Field called "Competitors" that is hard coded to only always return Accounts where Record Type = Competitor. Spring,Summer 09? |
|
rpr2 Aug 23 |
Merged Comment
originally posted Jun 5
I voted for this, but to clarify my need it is to hard code/set a DEFAULT filter, but have the ability to remove the default for specific searches when needed.
|
|
Scott_Jorgensen Aug 23 |
Merged Comment
originally posted Jun 5
rpr2 has the right idea here. The biggest need is to set a default. Making the filter mandatory is secondary (because it can already be handled by a validation rule).
In fact, if you had a default filter and a validation rule in place the results would be pretty good... what do you think? |
|
WrogWrog Aug 23 |
Merged Comment
originally posted Jun 6
"Yay!" and "but if only" indeed.
To me, this seems to be the same expression of disapointment as http://ideas.salesforce.com/article/show/25164/Filter_on_Lookup. |
|
dmsx2 Aug 23 |
Merged Comment
originally posted Jun 7
This is a super idea!
Having only a validation rule (or even an enhanced lookup plus validation rule) works from a data cleanliness side, but it doesn't make the user's experience any better. It would save a lot of clicks if the user didn't need to specify filter manually using an enhanced lookup, or to pick a new record if the validation rule fires, or to pick blindly if the SysAd didn't include the proper search lookup fields. So I agree with Scott that a default plus a validation rule would solve the problems. Anyone who tried to change the filter would just hit an error. |
|
agluewvrs Aug 23 |
Merged Comment
originally posted Jun 17
There's at least 3 other ideas that match this one:
Pre-defined Filters on Lookups (vs. user defined through the GUI)...so close...so close. |
track comments for this idea
Please log in to post a comment
last 100 promotions:
- joshnet101
- JoeMcV
- maksim
- mary_cilva
- jp_hess
- satellitemike
- nickbonich
- jmartin
- temhof
- supporties
- tmbarry
- sam@twkg
- CKZhou
- nathalie
- spanky340
- thepick
- amycm
- brad_huffman
- benoit
- marco_teulings
- ianr
- smccambridge
- jack_tinsley
- andreas_krebs
- greatg
- csidesinternap
- kelly_hardebeck
- Adama
- motu
- acumenuk
- ann_geerts
- 7/12/2007_23:55
- qingsong_li
- mark.evangelista05222008
- swheeldon@salesforce.com
- DPHSA
- aerometricjlb
- kchi
- mike_kreaden
- Jazz00711
- newby
- thomine
- huluadmin
- cermlich
- jayhunter
- proactive
- peter_bender
- slazarus
- seber
- J._Emma
- eurodicautom
- J_Keener
- jbivona08132008
- grueser
- sethwilliams
- marcbaizman
- initsysadmin
- jeregar
- testorg
- alliforce
- msnowden213
- jeffd703
- krzysztof_zych
- james_tran
- darqueness
- furufuru
- LindaABraham
- cased19
- devnv
- kmira
- advantagetitle
- robirl
- deepbluesea
- caelenba
- joshvh
- jamesan
- elizabeth_leath
- 7/1/2008_3:55
- lineagepower
- collabengine
- toddosc
- julianne
- jon_go
- hans-christoph_lang
- mottetpenrose
- ebesse
- aldicrmplc
- alex1975
- jamesweatherall
- bgrimes
- Etzy
- HLogan
- mpom
- jgvanbrabandt
- nikkig
- doncarlito
- tribe
- arnar_laufdal_olafsson
- astephenc
- cken
recently demoted by:
- phillv
- pran123
POST IDEA
Note for IdeaExchange Support: Seems that "Search Ideas" is not working correctly anymore in IdeaExchange. When I do a search on "lookup" I only get 4 hits, and idea 25164 is not included!