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

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 03.08.2017, 00:13   #1  
Blog bot is offline
Blog bot
Участник
 
25,617 / 848 (80) +++++++
Регистрация: 28.10.2006
stoneridgesoftware: How to Set up Required Dimensions in Dynamics 365 Business Edition
Источник: https://stoneridgesoftware.com/how-t...iness-edition/
==============

Dimensions are a powerful tool in Dynamics 365 Business Edition and Dynamics NAV. In this post, I specifically want to focus on how to set up Dimension Requirements – which is a way to ensure that you are enforcing the use of the desired dimensions on any given transaction.

About: Default Dimensions

Default Dimensions have two fundamental purposes:
  1. Default Dimensions can be assigned to master records (e.g. G/L Account, Customer, Item, Salesperson) and when those records are used in a transaction, it will be posted with those dimensions. For example, a Salesperson can have a Default Dimension AREA: Central.  Any Sales Orders that have that Salesperson will inherit a Dimension AREA: Central.  This will carry to the posted data (sales, shipment, invoice, G/L, et cetera) and can be used for reporting.
  2. In addition to setting defaults, the other thing Default Dimensions can do is require specific dimensions and even specific dimension values to be used. An example might be that all transactions that hit a Revenue G/L Account must include a DEPARTMENT dimension.


Walkthrough: Require DEPARTMENT Dimension on all Revenue G/L Accounts
  1. Open the Chart of Accounts
  2. Single or Multiple Accounts
    1. Single Account: Click on the individual G/L Account you wish to update.  In the Ribbon click Dimensions > Dimensions-Single
    2. Use the ellipsis to “Select More”, then use the Checkbox to select multiple accounts. In the Ribbon click Dimensions > Dimensions-Multiple
  3. Click +new to create new Default Dimension requirement.
  4. Select the Dimension Code that you want to be required. (In this example, DEPARTMENT)
  5. Leave Dimensions Value Code blank.
  6. Change Value Posting to Code Mandatory.
    1. Same Code is used if you only wanted a single Dimension Value Code to be allowed for the G/L Account(s). If you choose Same Code you would also select a specific Dimension Value Code.
    2. No Code is used if you wanted to prevent a particular dimension from being used with that G/L Account. One example is an expense-specific dimension to be prevented from use with revenue accounts.
  7. Click OK


You’ve now required the DEPARTMENT dimension to be used on any posting to the selected G/L Accounts.  You can verify this setup by creating a General Journal (or document, if preferred) and attempting to post without setting a Department Code.  Dynamics should stop you with an message similar to this:



Walkthrough: Require AREA Dimension on the Salesperson
  1. Open the Salespeople/Purchasers list
  2. Single or Multiple Accounts
    1. Single Account: Click on the individual G/L Account you wish to update.  In the Ribbon click Dimensions > Dimensions-Single
    2. Use the ellipsis to “Select More”, then use the Checkbox to select multiple accounts. In the Ribbon click Dimensions > Dimensions-Multiple
  3. Click +new to create new Default Dimension requirement.
  4. Select the Dimension Code that you want to be required. (In this example, AREA)
  5. Select a Dimensions Value Code that should always be used with this salesperson.
  6. Change Value Posting to Same Code.
  7. Click OK


You’ve now required that whenever this Salesperson is used, the AREA dimension will default to 70 on any transaction, but additionally, during posting the value will be tested to ensure that it is 70.  (Manual changes or other records with their own defaults won’t override.)

If two master records each have different values for the same Default Dimension (e.g. Both the Salesperson and Customer have a default AREA dimension), then the Default Dimension Priorities is the setup you want to use to dictate which should take priority.  We’ll save that topic for next time…

More Information

Источник: https://stoneridgesoftware.com/how-t...iness-edition/
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
stoneridgesoftware: How to Pull Data from Microsoft Dynamics 365 into Power BI Reports Blog bot DAX Blogs 0 19.07.2017 20:13
gustafwesterlund: Dynamics 365 Version 9.0 Business Edition and more Blog bot Dynamics CRM: Blogs 0 28.06.2017 20:12
stoneridgesoftware: Configuring Power BI Integration for Dynamics 365 Workspaces Blog bot DAX Blogs 1 07.03.2017 10:04
crminthefield: Podcast and Overview: Microsoft Dynamics CRM 2011 Update Rollup 14 Blog bot Dynamics CRM: Blogs 0 12.07.2013 07:13
crminthefield: Podcast and Overview: Microsoft Dynamics CRM 2011 Update Rollup 13 Blog bot Dynamics CRM: Blogs 0 27.03.2013 22:12

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

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

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 01:42.