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

Опции темы Поиск в этой теме Опции просмотра
Старый 10.01.2018, 05:11   #1  
Blog bot is offline
Blog bot
21,322 / 725 (67) +++++++
Регистрация: 28.10.2006
powerobjects: Dynamics 365 Development and Customization: Field Group Extensions

A new feature in the latest platform update for Dynamics 365 for Finance and Operations (Platform Update 11) that was released in October provides the ability to extend a field group that belongs to another model. This is a significant improvement as previously, there was no way of achieving this.

Prior to this enhancement, if you had a field group that belonged to a vertical or an add-on created in its own model and you wanted to add a custom field that you created, you had no option available to you. With this new feature, you now have that option. In this blog, we will walk through an example of how to implement this new feature and will provide a few observations along the way.


In this scenario, we’ll start with an existing field group that may have been created as part of a vertical solution and exists in a new model we’ll call ApplicationSuiteExtensioin. As you can see, the new package has references back to the ApplicationSuite package (as well as ApplicationPlatform and ApplicationFoundation, not seen).

In this model, a new field group has been added to the CustTable containing a new field as shown below. This new field group has also been added to the customer form.


Your company needs an additional reference field to be displayed in the same location where the ApplicationSuiteExtension model added one. Therefore, you will need to create a new field in your own package, and add it to the field group above. The first step is to create your new package/model, which we’ll call ApplicationSuiteExtension2. This new package must reference the ApplicationSuiteExtension  package which has the original field group, otherwise the field group in ApplicationSuiteExtension will not be available.

Create an extension of the CustTable in your model and add a new field called YourCustomerReference. Then add this field to the field group NewFieldGroup1, which will be accessible under the field group node.

You can now add this new field to the field group NewFieldGroup1 that exists in a different model.


That’s all there is to it! You can now add the field group to any form or report. Once completed, you’ll see that your new field is now available in the field group. This functionality was not possible prior to update 11.

For more helpful Dynamics 365 tips and tricks, be sure to subscribe to our blog!

Happy Dynamics 365’ing!

Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
alirazazaidi: Dynamics 365 for Finance and Operations Development Cookbook desi Review. Blog bot DAX Blogs 39 11.09.2018 16:30
survivingcrm: What’s An “App” in Dynamics 365 Anyway? Blog bot Dynamics CRM: Blogs 0 06.01.2018 22:14
powerobjects: PowerObjects’ Top 10 Most Popular Blog Posts of 2017 Blog bot Dynamics CRM: Blogs 0 15.12.2017 03:21
crminthefield: Podcast and Overview: Microsoft Dynamics CRM 2013 Update Rollup 2 Blog bot Dynamics CRM: Blogs 0 15.04.2014 01:15
wiki.dynamicsbook: Changes Made in Navision Attain 3.60 Blog bot Dynamics CRM: Blogs 0 02.09.2008 13:23
Опции темы Поиск в этой теме
Поиск в этой теме:

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

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

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

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