Ability to set default entity for lookup fields

[dnaedwards]

Please consider adding the ability to designate the default entity for lookup fields like Potential Customer on the Opportunity. We have several implementations where we might use the Account or Contact entity but not both. Additionally, clients might want to require or prefer a particular entity over another and want the lookup field to, at a minimum, default to the desired entity type.

I've had two client requests in the past week alone for this feature.

Thank you,

[D365Ideas_Admin]

Thank you for your feedback. This is a good suggestion! We will consider this in our roadmap.

Sincerely,

Srikumar Nair

PM, Microsoft

[dnaedwards]

This should cover the lookup dialog in all places, like when Set Regarding in Outlook as you cannot touch this via code. I could only think of doing this now in a supported way via a plugin on the Entity entity with RetrieveMultiple and resorting this data before it hits the dialog dropdown list but this is expensive from a processing point of view over thousands of requests.

[D365Ideas_Admin]

Setting the default (much like setting the default lookup view in other lookups) should be able to allow you to limit the type to either Account OR Contact - In my B:B customers like the railroad, they don't want opportunities created against Contacts. - Similarly, B:C organizations might want to ensure that opportunities are always created against the contact record. - Maybe that's asking for a 'unimorphic' relationship. 😉

[D365Ideas_Admin]

+1 for the ability to set this as a proper customisation and have it honoured by Outlook "set regarding" as well. In B2B scenarios I almost always end up with Opportunties having customer = Account and an additional lookup for decision maker (contact), nicely filtered where possible. For "regarding" it would be great to stop having to use scripts to set the list of entities available to the user* and set a default as well. I can see my extra wish being harder to implement though - regarding list is based on entities which can have activities under them, so if I customise the 'visible' regarding choices for (say) Appointments, then add a new custom entity, should the new entity default to being in the list or not? I recently resorted to an onLoad script to limit the list and set the default, but it's far from ideal and probably one of those horrid unsupported things we all want to avoid: document.getElementById("regardingobjectid").setAttribute("lookuptypes", "1,2,10020,...") document.getElementById("regardingobjectid").setAttribute("defaulttype", "10020") *I know security roles handle this in most cases, but not for users who are system admins, and in CRM Online there's always one of those, since customers are reluctant to pay for a "ghost" user just to declutter their interface. There are also many occasions when some activity types simply don't belong under some entities because of business process or rules, but CRM does not have that distinction available via activity pointer.

[n2]

Yes, please give us the ability to set the Default, for all the reasons given below. As well as the abilty to restrict it to ONLY Accounts or Contacts.

[D365Ideas_Admin]

I have read on several MS CRM blogs, developers customize the Customer look-up, to ONLY select Acount OR Contact as per needs. I just hope that this is not workaround but an unsupported customization.

[D365Ideas_Admin]

Thank you for your feedback. This is a great suggestion, and we will consider this in our roadmap. thanks Anusha Shankar

[D365Ideas_Admin]

I have had more than a dozen requests to do this...and the 2013 inline lookup takes even more actions to choose a contact because you first have to scroll to the bottom of the list and then select Look Up More Records to even get to the lookup, then you still have to change from Account to Contact before you can select your contact. So 2013 is even more painful than 2011 was in this regard.

[D365Ideas_Admin]

As a top 10 item on Connect that has been here now for more than 2.5 YEARS I disappointed that this still hasn't been addressed with CRM 2015. What is the point of the new "rapid release cadence" if things like this are continuously ignored?

[D365Ideas_Admin]

Way too long on roadmap.