{"id":20637,"date":"2019-10-01T11:41:10","date_gmt":"2019-10-01T11:41:10","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=20637"},"modified":"2022-07-21T12:08:10","modified_gmt":"2022-07-21T06:38:10","slug":"tip-to-filter-customer-field-depending-on-type-of-customer-in-dynamics-365-uci","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2019\/10\/tip-to-filter-customer-field-depending-on-type-of-customer-in-dynamics-365-uci\/","title":{"rendered":"Tip to Filter Customer Field depending on \u2018Type of Customer\u2019 in Dynamics 365 UCI"},"content":{"rendered":"

Introduction<\/h2>\n

Recently, we faced an issue in UCI where we had to filter customer field depending on Type of customer.<\/p>\n

Here, the requirement was as follows:<\/p>\n

If the type of customer is account then the customer field should show Account entity records only.<\/p>\n

If the type of customer is contact then the customer field should show Contact entity records only.<\/p>\n

For this, we had an option set field named \u2018Type of customer\u2019 which contains \u2018contact\u2019 and \u2018account\u2019 option.<\/p>\n

We had added a JavaScript function to set entity type according to value of \u2018Type of customer\u2019 field using setEntityTypes function as shown in following code:<\/p>\n

 function onLoad(executionContext) {\r\n    try {\r\nvar formContext= executionContext.getFormContext();\r\nformContext.getControl(\"customerid\").addPreSearch(filterCustomerLookup);\r\n    } catch (e) { }\r\n}\r\n\r\nfunction filterCustomerLookup(executionContext) {\r\n    try {\r\n        \tvar formContext= executionContext.getFormContext();\r\n        if (formContext.getAttribute(\"new_customertype\").getValue() == 100000001) {\r\n            formContext.getControl(\"customerid\").setEntityTypes([\"account\"]);\r\n\t} else {\r\n            formContext.getControl(\"customerid\").setEntityTypes([\"contact\"]);\r\n         }\r\n    } catch (e) { }\r\n}\r\n<\/pre>\n
This function was working in Classic web UI, but on UCI, the customer was not being filtered correctly.
\nFor example, in our case, \u2018contact\u2019 was default value of \u2018Type of customer\u2019 and when we were changing \u2018Type of customer\u2019 field value from Contact to Account and clicking on search button of Customer field we were getting Contact records instead of Account records.<\/p>\n
Shown in below screenshot is the Records in customer lookup on selecting customer Type Contact:<\/p>\n
\"Customer<\/p>\n
Shown in below screenshot is the Records in customer lookup on selecting customer Type Account:<\/p>\n
\"Customer<\/p>\n
So, we removed the pre-search and tried using below function on Load and on Change of \u2018Type of Customer\u2019 field.<\/p>\n
function onChangeOfTypeOfCustomer(executionContext) {\r\n    try {\r\nvar formContext= executionContext.getFormContext();\r\n        if (formContext.getAttribute(\"new_typeofcustomer\").getValue() == 100000001) {\/\/100000001 value if Account option in Type of customer field\r\n            formContext.getControl(\"customerid\").setEntityTypes([\"account\"]);\r\n        } else {\r\n            formContext.getControl(\"customerid\").setEntityTypes([\"contact\"]);\r\n        }\r\n    } catch (e) {   }\r\n}<\/pre>\n
Again these changes were working in Classic web UI but on UCI, customer was being filtered only for the default entity type.
\nFor example, in our case contact was default value of \u2018Type of customer\u2019 and when we clicked on new \u2018Type of customer\u2019 field value was being set to Contact by default. As a result, only contact entity was set in Customer field entity types using following code:
\nformContext.getControl(“customerid”).setEntityTypes([“contact”]);
\nWe were getting records of contacts as shown below:<\/p>\n
\"Customer
\nBut, when we were changing \u2018Type of customer\u2019 field value to \u2018Account\u2019, it was not showing any account record and keeps showing \u2018Loading\u2019 text forever, even though we set account entity in Customer field entity types using following code.<\/p>\n
formContext.getControl(“customerid”).setEntityTypes([“account”]);<\/p>\n
\"Customer<\/p>\n
On further checking, we observed that this was due to function on \u2018onLoad\u2019 event was directly setting entity type.<\/p>\n
So for handling customer type on load event, we had to combine the first original code with changed code.<\/p>\n
The final working solution is as below:<\/p>\n
Function on Change event of Customer Type field<\/strong>:<\/p>\n
function onChangeOfCustomerType(executionContext) {\r\ntry {\r\n\r\nvar formContext= executionContext.getFormContext();\r\n\r\nif (formContext.getAttribute(\"new_customertype\").getValue() == 100000001) {\r\nformContext.getControl(\"customerid\").setEntityTypes([\"account\"]);\r\n} else {\r\nformContext.getControl(\"customerid\").setEntityTypes([\"contact\"]);\r\n}\r\n\r\n} catch (e) {\r\n\r\n}\r\n\r\n}<\/pre>\n
Function on \u201conLoad\u201d event of form:<\/strong><\/p>\n
 function setCustomerTypeOnLoad(executionContext) {\r\n    try {\r\n        var formContext= executionContext.getFormContext();\r\n        formContext.getControl(\"customerid\").addPreSearch(filterCustomerLookup);\r\n    } catch (e) {    }\r\n}\r\nfunction filterCustomerLookup(executionContext) {\r\ntry {\r\nvar formContext= executionContext.getFormContext();\r\nif (formContext.getAttribute(\"new_customertype\").getValue() == 100000001) {\r\nformContext.getControl(\"customerid\").setEntityTypes([\"account\"]);\r\n} else {\r\nformContext.getControl(\"customerid\").setEntityTypes([\"contact\"]);\r\n}\r\n} catch (e) { }\r\n}<\/pre>\n
Conclusion<\/h2>\n
Thus, with the above code you can easily filter customer field in Dynamics 365 UCI depending upon Type of Customer.<\/p>\n
70% of global 2000 companies apply gamification to improve productivity and returns!<\/div><\/div><\/h2>\n
Gamifics365<\/a> <\/strong>\u2013 Spin the magic of games within Microsoft Dynamics 365 CRM to improve user adoption, enhance productivity, and achieve company goals!<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
Introduction Recently, we faced an issue in UCI where we had to filter customer field depending on Type of customer. Here, the requirement was as follows: If the type of customer is account then the customer field should show Account entity records only. If the type of customer is contact then the customer field should\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":20648,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[59,60],"tags":[1953,1952],"class_list":["post-20637","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uci","category-unified-interfaceuci","tag-dynamics-365-uci","tag-unified-interfaceuci"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/20637","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=20637"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/20637\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/20648"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=20637"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=20637"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=20637"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}