{"id":25725,"date":"2020-11-23T15:01:05","date_gmt":"2020-11-23T15:01:05","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=25725"},"modified":"2023-01-13T14:08:00","modified_gmt":"2023-01-13T08:38:00","slug":"use-of-dynamics-365-crm-field-service-features-functional-locations-and-asset-hierarchy","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2020\/11\/use-of-dynamics-365-crm-field-service-features-functional-locations-and-asset-hierarchy\/","title":{"rendered":"Use of Dynamics 365 CRM Field Service features – Functional Locations and Asset Hierarchy"},"content":{"rendered":"

Introduction<\/strong><\/h1>\n

The field service organizations related to healthcare and manufacturing sectors will not have a fixed location for their devices. This means that the technician might spend the first few hours just trying to find the item on which they need to work upon while on the field.<\/p>\n

When workstations are large and complex, it is very important that technicians must be aware beforehand where exactly they need to go to perform their field service work.<\/p>\n

In 2020 release wave 2, \u201cAsset hierarchy and location\u201d feature is now enabled on the Account entity. With the help of this feature, you can model your customer\u2019s exact asset location. For example, you can model your asset location with a hierarchy that includes Building, Floor, and HVAC Room.<\/p>\n

To use this feature, make sure you have field service updated to v8.8.x or higher version.<\/p>\n

To explore this feature create Service Account first, as service account is important to create a work order and define customer and service location on a work order.<\/p>\n

On Service Account there is a tab called \u201cAssets and Locations\u201d on the Account form.<\/p>\n

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

This is the Functional location entity used to create the hierarchy on Account.<\/p>\n

You can very quickly add functional locations by right-clicking on the ellipse on the right side and selecting \u2018+ New Location\u2019 as shown below:<\/p>\n

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

Give a name for Physical\/Functional location as shown below:<\/p>\n

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

Once saved, add the \u201cBuilding 1125\u201d location under Account.<\/p>\n

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

Note: To see the created functional location in the hierarchy you need to click on \u201cAdd Existing Location\u201d by right-clicking on the ellipse.<\/em><\/strong><\/p>\n

You can also observe this created functional location in a related tab called Functional Locations as shown below:<\/p>\n

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

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

In the same way, go on adding functional locations or assets by right-clicking on the ellipse on the right side of the added functional location and select \u2018+ New Location\u2019 and\/or \u2018New Asset\u2019 respectively as shown in the below screenshot:<\/p>\n

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

Now create a Location hierarchy as per the need.<\/p>\n

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

Next, add asset by right-clicking on the ellipse on the right side and selecting \u2018+ New Asset\u2019 as shown below:<\/p>\n

\"Next,<\/a><\/p>\n

\"Next,<\/a><\/p>\n

Once saved, the Asset will appear as shown in the below hierarchy:<\/p>\n

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

Go on adding assets using \u201cNew Asset\u201d and create an Asset hierarchy as per the need. You can add Asset under Parent asset as well, just as shown below:<\/p>\n

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

The moment you add any asset, the \u201cShow assets\u201d checkbox will be selected automatically. You can uncheck this any time you want to hide asset hierarchy.<\/p>\n

You can also observe these created customer assets in a related tab called Customer Assets as shown below:<\/p>\n

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

Drag and Drop feasibility<\/strong><\/h2>\n

You can move functional locations around by\u00a0dragging and dropping<\/em>\u00a0them on screen.<\/p>\n

Let say, one of my assets (AC 1002) shifted recently from Building 1125 location to Building 1126 location. Then just I will just drag it from the old location and drop\/place it on the new location, as shown below:<\/p>\n

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

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

Conclusion<\/strong><\/h1>\n

In this way, you can use FunctionalLocations for creating asset location hierarchy and can easily associate them to Service Accounts.<\/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":"

Introduction The field service organizations related to healthcare and manufacturing sectors will not have a fixed location for their devices. This means that the technician might spend the first few hours just trying to find the item on which they need to work upon while on the field. When workstations are large and complex, it\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":[545,592,805,806],"class_list":["post-25725","post","type-post","status-publish","format-standard","hentry","category-dynamics-365","category-dynamics-crm","category-field-service-2","tag-dynamics-365-crm","tag-dynamics-crm","tag-field-service","tag-field-service-dynamics-365"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/25725","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=25725"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/25725\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=25725"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=25725"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=25725"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}