{"id":24965,"date":"2020-10-02T11:34:47","date_gmt":"2020-10-02T11:34:47","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=24965"},"modified":"2023-01-13T14:08:18","modified_gmt":"2023-01-13T08:38:18","slug":"dynamically-filter-the-lookup-on-field-service-mobile-app","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2020\/10\/dynamically-filter-the-lookup-on-field-service-mobile-app\/","title":{"rendered":"Dynamically filter the lookup on Field Service Mobile App"},"content":{"rendered":"

The Field Service Mobile app helps organizations to deliver services to customer locations. It provides the ability to work on the Bookings by the Technician i.e. Bookable Resource.<\/p>\n

This application includes various features to automate the process so that technicians can work efficiently and flawlessly. In this blog, we will walk through the ability to dynamically filter the lookup in the Field Service Mobile app using updateLinkItemViews<\/strong> function.<\/p>\n

Consider this example: we have to filter out Company Name<\/strong> lookup on Contact based on City<\/strong> field value. Therefore, whenever the City<\/strong> on the Contact form is updated, Company Name<\/strong> lookup should be filtered out with the Accounts containing City <\/strong>as City of the Contact record.<\/p>\n

Please find the below steps to follow to achieve our considered request:<\/p>\n

    \n
  1. Customize contact form to include the Company Name<\/strong> (parentcustomerid) and City <\/strong>fields as shown in the below screenshot.\"Dynamically<\/a><\/li>\n

    <\/p>\n

  2. Add HTML and script within Offline HTML section, this includes the logic to bind the dynamic filters to the lookup on the form.
    \n
    \nAccountFilter.HTML:<\/strong> This html includes reference to the Javascript file as we can add only HTML file on the form. Below is the code snippet for the same.<\/p>\n

    <!DOCTYPE html><\/p>\n

    <html xmlns=”http:\/\/www.w3.org\/1999\/xhtml”><\/p>\n

    <head><\/p>\n

    <title><\/title><\/p>\n

    <script type=”text\/javascript” src=”JSBridge.js”><\/script><\/p>\n

    <script type=”text\/javascript” src=”JSBridgeExtension.js”><\/script><\/p>\n

    <script type=”text\/javascript” src=”Schema.js”><\/script><\/p>\n

    <script type=”text\/javascript” src=”Common.js”><\/script><\/p>\n

    <script type=”text\/javascript” src=”Enums.js”><\/script><\/p>\n

    <script type=”text\/javascript” src=”Telemetry.js”><\/script><\/p>\n

    <script type=”text\/javascript” src=”FilterAccount.js” ><\/script><\/p>\n

    <\/head><\/p>\n

    <body onload=”AccountFilter();”><\/p>\n

    <\/body><\/p>\n

    <\/html><\/p><\/blockquote>\n

    FilterAccount.js:<\/strong>\u00a0 This includes the business logic for filtering the Company Name<\/strong> lookup based on the City<\/strong> value entered on the Contact Form. Below is the code snippet for the same.<\/p>\n

    function AccountFilter() {<\/p>\n

    try {<\/p>\n

    \/\/ Change the parent customer on currently edited contact entity<\/p>\n

    MobileCRM.UI.EntityForm.onChange(function (entityForm) {<\/p>\n

    if (entityForm.context.changedItem != “address1_city”) return;<\/p>\n

    MobileCRM.UI.EntityForm.requestObject(function (entityForm) {<\/p>\n

    \/\/ Take detail view with name “General”<\/p>\n

    var detailsView = entityForm.getDetailView(“General”);<\/p>\n

    var inlineSetup = new MobileCRM.UI.DetailViewItems.LookupSetup();<\/p>\n

    var City = entityForm.entity.properties.address1_city;<\/p>\n

    inlineSetup.addView(“account”, “Default”, true);<\/p>\n

    \/\/ Alternatively, specify the explicit fetch XML filter for inline lookup<\/p>\n

    inlineSetup.addFilter(“account”, ‘<fetch version=”1.0″><entity name=”account”><attribute name=”name” \/><attribute name=”primarycontactid” \/><attribute name=”telephone1″ \/><attribute name=”accountid” \/><order attribute=”name” descending=”false” \/><filter type=”and <condition attribute=”address1_city” operator=”eq” value=”‘ + City + ‘” \/> <condition attribute=”statecode” operator=”eq” value=”0″ \/><\/filter><\/entity><\/fetch>’);<\/p>\n

    dialogSetup = new MobileCRM.UI.DetailViewItems.LookupSetup();<\/p>\n

    dialogSetup.addView(“account”, “Default”, true);\u00a0 \/\/ Set “Default” view for expanded lookup form<\/p>\n

    dialogSetup.addFilter(“account”, ‘<fetch version=”1.0″><entity name=”account”><attribute name=”name” \/><attribute name=”primarycontactid” \/><attribute name=”telephone1″ \/><attribute name=”accountid” \/><order attribute=”name” descending=”false” \/><filter type=”and <condition attribute=”address1_city” operator=”eq” value=”‘ + City + ‘” \/> <condition attribute=”statecode” operator=”eq” value=”0″ \/><\/filter><\/entity><\/fetch>’);<\/p>\n

    dialogOnly = false; \/\/ Allow both inline lookup and expanded lookup dialog<\/p>\n

    \/\/ Allow both inline lookup and expanded lookup dialog<\/p>\n

    detailsView.updateLinkItemViews(0, dialogSetup, inlineSetup, dialogOnly);<\/p>\n

    }, null, null);<\/p>\n

    },<\/p>\n

    function (error) {<\/p>\n

    MobileCRM.bridge.alert(“An error occurred: ” + error);<\/p>\n

    },null);\u00a0 }<\/p>\n

    catch (err) {<\/p>\n

    MobileCRM.bridge.alert(err);<\/p>\n

    }<\/p>\n

    }<\/p><\/blockquote>\n<\/li>\n

  3. Once completed with adding offline html, we need to include the AccountFilter.html<\/strong> file on the Contact Form by adding an Iframe as shown in the below screenshot.
    \n    \"Dynamically<\/a><\/li>\n

    <\/p>\n

  4. Save and close the form and Publish the Mobile project to reflect the customizations in the Field Service Mobile App.<\/li>\n
  5. Now Sync the Field Service Mobile app and navigate to the Contact record. Change the City<\/strong> on the contact and click on the Company Name<\/strong> lookup. This will filter and display the accounts containing the City<\/strong> as that of the City of the contact.As shown in the below screenshot, we have added City<\/strong> as Clinton<\/strong> then the Company Name lookup will filter the accounts containing the City<\/strong> as Clinton<\/strong>.\"Dynamically<\/a><\/li>\n<\/ol>\n

    Conclusion<\/strong><\/h2>\n

    Field Service provides us the flexibility to achieve our business requirements by filtering lookups using updateLinkItemViews<\/strong> function within Field Service Mobile App.<\/p>\n

    Need any help with Microsoft Dynamics 365 Field Service module \/ Microsoft CRM \/ Power Platform development?<\/div><\/div><\/h3>\n

    Want to manage your field services portal more effectively? Contact us at crm@inogic.com<\/a> and our Inogic- Professional Services Division<\/a> will help you modify, optimize, and automate all our requirements within Microsoft Dynamics 365 Field Service!<\/em><\/p>\n

    Happy Servicing!<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

    The Field Service Mobile app helps organizations to deliver services to customer locations. It provides the ability to work on the Bookings by the Technician i.e. Bookable Resource. This application includes various features to automate the process so that technicians can work efficiently and flawlessly. In this blog, we will walk through the ability to\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":[16,19,27],"tags":[2079,545,2020,1978,1890],"class_list":["post-24965","post","type-post","status-publish","format-standard","hentry","category-dynamics-365","category-dynamics-crm","category-field-service-2","tag-dynamic-filter","tag-dynamics-365-crm","tag-dynamics-365-crm-field-service-mobile-app","tag-dynamics-365-field-service-mobile-app","tag-field-service-mobile-app"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/24965","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=24965"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/24965\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=24965"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=24965"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=24965"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}