AXForum  
Вернуться   AXForum > Microsoft Dynamics CRM > Dynamics CRM: Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск Все разделы прочитаны

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 05.12.2017, 06:13   #1  
Blog bot is offline
Blog bot
Участник
 
19,715 / 665 (62) +++++++
Регистрация: 28.10.2006
powerobjects: List of Values: OptionSet vs. Lookup in Enterprise Solutions
Источник: https://www.powerobjects.com/2017/12...ise-solutions/
==============


To OptionSet or not to OptionSet? That is the question…of this blog post anyways!

There are many times, especially in the Enterprise space, where a decision must be made on how to implement Lists of Values (LOVs). For example, maybe you have Company Type and Company Sub-Type fields that need to have a list of values to select from. This can be implemented in a multitude of ways, but for the sake of this blog, let’s say you have narrowed it down to two: OptionSets or Lookup tables. (Spoiler Alert: we recommend Lookups)

Lookup tables will grant you a few extra benefits that you won’t receive with OptionSets. First, you have the ability to dynamically filter based on another field without JavaScript! In our example from above, you can narrow down which Company Sub-Types are available based on the Company Type selected. Did we mention that it can be done without code?

Second, the integration/migration points from other systems (SAP, Siebel, Dynamics AX/GP/SL, etc.) becomes dramatically easier. If you are working on communicating with another system that provides the actual values in the LOVs, you can now insert these rows into Dynamics as data instead of Metadata. That means a solution push is not required every single time there is an addition/update/removal of a value within the LOV! How cool is that? No going through the IT deployment process just to be able to change the values that are being fed from a different system.

Last, we find the ability to see/update all LOVs in one place is much less cumbersome than having to go to each individual field or Global OptionSet to see what the values are and whether they are current.

We do feel like more end users are probably used to the idea of a pick list vs. a lookup control, but with more use comes comfort. The benefits of using Lookups more than make up for the fact that you will need to re-train end users on how to fill out these kinds of fields.

If you enjoyed this post, be sure to check out the rest of our Dynamics 365 blogs or sign up for one of our awesome Dynamics 365 events or webinars!


Happy Dynamics 365’ing!



Источник: https://www.powerobjects.com/2017/12...ise-solutions/
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
powerobjects: Financial Period Closing in Dynamics 365 for Finance and Operations Enterprise edition Blog bot DAX Blogs 0 29.11.2017 00:11
Leon's CRM Musings: Dialog Lookup Values For Common Entities Blog bot Dynamics CRM: Blogs 0 21.01.2014 20:11
Solutions Monkey: Microsoft Dynamics AX 2012 Enterprise Portal Performance Tips Blog bot DAX Blogs 0 31.01.2012 06:16
CRM DE LA CREME! Some more useful javascripts for MS CRM Blog bot Dynamics CRM: Blogs 0 04.05.2010 11:05
Solutions Monkey: Enterprise Portal Screencasts at Channel9.msdn.com Blog bot DAX Blogs 6 01.07.2008 19:38
Опции темы Поиск в этой теме
Поиск в этой теме:

Расширенный поиск
Опции просмотра

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 11:22.
Powered by vBulletin® v3.8.5. Перевод: zCarot
Контактная информация, Реклама.