{"id":889,"date":"2014-09-08T12:05:34","date_gmt":"2014-09-08T06:35:34","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=889"},"modified":"2021-08-25T11:09:27","modified_gmt":"2021-08-25T11:09:27","slug":"add-custom-view-in-lookup-and-disable-all-the-other-views","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2014\/09\/add-custom-view-in-lookup-and-disable-all-the-other-views\/","title":{"rendered":"Add Custom View in Lookup and Disable all the other Views"},"content":{"rendered":"

We had a requirement in which we were supposed to use a addCustomView<\/strong> method in order to filter the Lookup. We came across a situation in which we were able to set the custom view(The view with filtered records) as a default view to restrict the users from choosing the other records, but if a user wants, he\/she could choose the different view from the Lookup window dialog and select the other records too, which the users were not supposed to choose.<\/p>\n

Let us first introduce you to the situation, on the Quote form we have a Lookup field called Project Template<\/strong>. And, on the Quote Product form we have another Lookup field called Project Template Items<\/strong> which should be filtered as per the value chosen for the Project Template<\/strong>.<\/p>\n

We`ll start from the point where we have the ID <\/strong>of the chosen Project Template<\/strong>(to get the ID, you need to write a script on the Load of the Quote Product form).<\/p>\n

Initially, what we started off was adding our custom view, but it still allowed the user to switch between different views, as a result users were able to choose records from other views.<\/p>\n

We`ll explain you both the situations, the Initial Situation<\/strong>(which was adding the custom view) and the Ideal Situation<\/strong>(which was adding the custom view and restricting users from selecting other view) .<\/p>\n

First and foremost, for the Lookup that`ll have filtered values, you need to change the below properties. These are the necessary steps.<\/p>\n

Step 1: <\/strong><\/p>\n

From the form editor, go to the properties of the Lookup field.<\/p>\n

Step 2:<\/strong><\/p>\n

\"1\"<\/a><\/p>\n

In the Additional Properties <\/strong>section,<\/p>\n

Default View – Select a View.<\/p>\n

View Selector – Choose “Show Selected Views<\/strong>“.<\/p>\n

System Views\u00a0 – Only Select the view which was selected in the Default view.<\/p>\n

Initial Situation<\/strong>:<\/strong><\/p>\n

In this situation, we were doing everything right but, we missed something that stopped us from getting the ideal output.<\/p>\n

Code<\/strong><\/p>\n

function setCustomView(projectTemplateId) {<\/p>\n

var functionName = “setCustomView”;<\/p>\n

try {<\/p>\n

\/\/Check whether the field exist or not<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 if (isValid(Xrm.Page.getControl(“new_projecttemplateitemid”))) {<\/p>\n

\n

\/\/ add the randomly generated GUID for the view id
\nvar viewId = ‘{00000000-0000-0000-0000-000000000001}’;<\/p>\n<\/div>\n

 <\/p>\n

\/\/add the entity name<\/p>\n

var entityName = “new_projecttemplateitem”;<\/p>\n

 <\/p>\n

\/\/ add the view display name<\/p>\n

var viewDisplayName = “Project Template Item Lookup View”;<\/p>\n

 <\/p>\n

\/\/ fetch xml for filtered Project Template Item records<\/p>\n

var fetchXml = “<fetch version=’1.0′ output-format=’xml-platform’ mapping=’logical’ distinct=’false’> ” +<\/p>\n

“<entity name=’new_projecttemplateitem’>” +<\/p>\n

“<attribute name=’new_name’ \/>” +<\/p>\n

“<filter type=’and’>” +<\/p>\n

“<condition attribute=’new_projecttemplate’ operator=’eq’ value='” + projectTemplateId + “‘ \/>” +<\/p>\n

“<\/filter>” +<\/p>\n

“<\/entity>” +<\/p>\n

“<\/fetch>”;<\/p>\n

 <\/p>\n

\/\/Grid Layout for filtered records<\/p>\n

var layoutXml = “<grid name=’resultset’ object=’1′ jump=’productid’ select=’1′ icon=’1′ preview=’1′>” +<\/p>\n

“<row name=’result’ id=’new_projecttemplateitemid’>” +<\/p>\n

“<cell name=’new_name’ width=’150′ \/>” +<\/p>\n

“<cell name=’createdon’ width=’150′ \/>” +<\/p>\n

“<\/row>” +<\/p>\n

“<\/grid>”;<\/p>\n

 <\/p>\n

\/\/ add the custom view for the lookup field<\/p>\n

Xrm.Page.getControl(“new_projecttemplateitemid”).addCustomView(viewId, entityName, viewDisplayName, fetchXml, layoutXml, true);<\/p>\n

}<\/p>\n

} catch (e) {<\/p>\n

throwError(e, functionName);<\/p>\n

}<\/p>\n

}<\/p>\n

 <\/p>\n

In the above code everything was right but,<\/p>\n

on selecting the Custom view, we were getting the below results:<\/p>\n

\"2\"<\/a><\/p>\n

And, on selecting the System View, we were getting the below results.<\/p>\n

\"3\"<\/a><\/p>\n

Both the views were giving us different results, which we never wanted.<\/p>\n

 <\/p>\n

So, in the search of an ideal situation we found the below solution.<\/p>\n

Ideal Situation<\/strong>:<\/strong><\/p>\n

Replace the code in the box with the below code.<\/p>\n

Code<\/strong><\/p>\n

\/\/ add the default View GUID for the view id<\/p>\n

var viewId = Xrm.Page.getControl(“new_projecttemplateitemid”).getDefaultView();<\/p>\n

This single piece of line works like a charm.<\/p>\n

Now, we got the below results on selecting both the views.<\/p>\n

Custom View<\/strong>:<\/p>\n

\"4\"<\/a><\/p>\n

System View:<\/strong><\/p>\n

\"5\"<\/a><\/p>\n

 <\/p>\n

And, this is how we got the desirable result with a small tweak in the code.<\/p>\n

Free 70% of storage space in CRM with Attachment Management Apps!<\/div><\/div><\/h2>\n

Attach2Dynamics<\/a> – Store and manage documents\/attachments in cloud storage of your choice – SharePoint, Dropbox or Azure Blob Storage from within Dynamics 365 CRM.<\/em>
\nSharePoint Security Sync<\/a><\/strong> \u2013 Robust and secure solution to integrate Dynamics 365 CRM and SharePoint Security Sync thereby ensuring secure access to confidential documents stored in SharePoint.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

We had a requirement in which we were supposed to use a addCustomView method in order to filter the Lookup. We came across a situation in which we were able to set the custom view(The view with filtered records) as a default view to restrict the users from choosing the other records, but if a\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[19,21,22,24],"tags":[456,1012,1790],"class_list":["post-889","post","type-post","status-publish","format-standard","hentry","category-dynamics-crm","category-dynamics-crm-2013","category-dynamics-crm-2015","category-dynamics-crm-2016","tag-custom-view","tag-lookup","tag-views"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/889","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=889"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/889\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=889"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=889"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=889"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}