{"id":4548,"date":"2017-02-22T16:38:14","date_gmt":"2017-02-22T11:08:14","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=4548"},"modified":"2017-02-22T16:38:14","modified_gmt":"2017-02-22T11:08:14","slug":"controls-in-dynamics-365-for-mobile-app-auto-complete","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2017\/02\/controls-in-dynamics-365-for-mobile-app-auto-complete\/","title":{"rendered":"Controls in Dynamics 365 for Mobile App: Auto-Complete"},"content":{"rendered":"

\"Auto<\/p>\n

In our previous blogs of the \u2018Controls in Dynamics 365 for Mobile App\u2019 series, we discussed Input Mask<\/a>, Multimedia<\/a> and Website Preview Control<\/a>. Website Preview Control allow users to get a brief description of the URL they enter in the \u2018Website\u2019 field right within Dynamics 365 Mobile and Tablet app. Today, let us discuss Auto-Complete Control.<\/p>\n

How Auto-Complete Control can be useful to the users?<\/strong><\/p>\n

We all love and use the \u2018Auto-Complete\u2019 feature available in almost all smartphones these days. Auto-Complete Control is something similar for fields in Dynamics 365 Mobile and Tablet app. On the go Sales person can use this control to save time while entering details like City, State, Business Type, etc.<\/p>\n

Let us see an example to understand how we can add Auto-Complete Control to a field;<\/strong><\/p>\n

In the following example we want to add the Auto-Complete Control to a custom string field, \u2018Secondary Contact\u2019 and \u2018Address 1: State\/Province\u2019 field on the Account entity.
\n<\/strong><\/p>\n

1. We will first add a string field as \u2018Secondary Contact\u2019 on the Account entity form and click on Change Properties;<\/p>\n

\"Auto<\/p>\n

2. We will now add the \u2018Auto-Complete\u2019 control and select the source option;<\/p>\n

\"Auto<\/p>\n

3. There are two options available for the source:<\/p>\n

A. View<\/strong><\/p>\n

B. Option Set<\/strong><\/p>\n

4. \u2018View\u2019 option will allow you to select any entity- view as a data source for the Auto Complete field. In this example we have selected the OOB entity Contacts and Active Contacts view as seen below;<\/p>\n

\"Auto<\/p>\n

5. Then it is mandatory to select a field to bind\/map value on \u2018Secondary Contact\u2019 field as a data source. This will list out all the string fields available in the selected entity view.<\/p>\n

\"Auto<\/p>\n

6. On the Dynamics 365 Mobile and Tablet app, user can now enter characters in the Secondary Contact field to search and can select the name from the list as seen below;<\/p>\n

\"Auto<\/p>\n

7. Users can also bind predefined Option Set of an entity as a data source. For example, we have created a custom Option Set for State and have chosen the Option Set as a source for \u2018Address 1: State\/Province\u2019 field.<\/p>\n

8. We can choose the Option Set, \u2018State\u2019 from the provided list as seen below;<\/p>\n

\"Auto<\/p>\n

9. Once the control is added, we will enter the State name in the field on the Dynamics 365 Mobile and Tablet app. It will detect the entered characters and filter out the list as seen below;<\/p>\n

\"Auto<\/p>\n

Conclusion<\/strong>:<\/p>\n

The Auto-Complete Control filters a list as you type and lets you select a value from the drop-down list rather than typing whole text. It is helpful for on the go users to save time while entering data on the Dynamics 365 Mobile and Tablet app.<\/p>\n

\n

Boost user adoption of Dynamics CRM\/365 with User Adoption Monitor<\/a> and User Gamification Module<\/a>!<\/strong><\/em><\/span><\/p>\n<\/blockquote>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

In our previous blogs of the \u2018Controls in Dynamics 365 for Mobile App\u2019 series, we discussed Input Mask, Multimedia and Website Preview Control. Website Preview Control allow users to get a brief description of the URL they enter in the \u2018Website\u2019 field right within Dynamics 365 Mobile and Tablet app. Today, let us discuss Auto-Complete\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":4553,"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":[13,40],"tags":[180,341],"class_list":["post-4548","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-customizations","category-mobile-controls","tag-auto-complete-controls-in-dynamics-365","tag-controls-in-dynamics-365"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/4548","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=4548"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/4548\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/4553"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=4548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=4548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=4548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}