Skip to main content

#msdyn365bc - Allowed Dimension Values.

Hi Readers,

This Week We will spend some time with what's new in #Msdyn365bc 2021 Release Wave 1. 

In this article we will understand about Enhancements in Default Dimensions.

Default Dimensions are part of the base functionality of the product for so many years. 

With This change Microsoft tried to solve one of the feature that was requested by customers.

Let's understand what is available and how to utilize it.

Summary - 

  • Open Business Central.
  • Navigate to a Master record where we can assign Default Dimension like Vendor.
  • Choose a Vendor and Select Dimension from Vendor Menu, Dimensions.
  • You will see a New Field Available in Default Dimension Page - Allowed Value Filter.
  • Based on this field value system will review dimension in transaction.

What was available? 

  • There are different ways that we can setup Default Dimension in #msdyn365bc.
  • You Can Choose Value Posting to be  - No Code, Same Code & Code Mandatory.
  • With Code Mandatory User will have to choose a Value for the dimension during the transaction.

What Changed with this feature?

  • The New Functionality only works if you have set Value Posting as - Code Mandatory.
  • In scenario where you would like user to have the dimension specified in transaction but also want to limit which dimension value they can use, you can use the New field Allowed Value Filter.
  • Dimension Selected in Allowed Value Filter will be the dimensions that user can use in transaction for that dimension.

Demo (** Data may vary based on environment where you are setting this up) - 

  • Open a Master Record, Vendor 10000 and Choose Dimension.

  • In Default Dimension Page set the Allowed Values Filter for Area Dimension (as its set to code mandatory).

  • Based on Selection, The Allowed Values Filters field will be populated.


  • Based on the setup above, When user uses vendor in a transaction system will auto populate value of Area to be 70 (as defined in Dimension Value Code Field). 
  • User can only change the Area Dimension value in transaction from - 30 or anything between 70 & 80.

  • Create a Purchase order for the vendor and change the Area Dimension to be 10.


  • Try Posting Purchase order.
  • System will generate a error message, - Dimension Value AREA, 10 is not allowed for Vendor, 10000.


This was discussed in last #bcopendiscussion. Please find below the recording of #bcopendicsussion.


Hope you understand the new Functionality in #msdyn365bc.

Let me know your views as comment to article.

Regards,
Saurav Dhyani
www.sauravdhyani.com
Labels:
Location: House No. 1, Shivlok Colony, 2, near Himalayan Academy Post Office, Shivlok Colony, Sewla Kalan, Majra, Dehradun, Uttarakhand 248171, India

Comments

  1. V BahetiApril 28, 2021 at 6:30 AM

    Thanks, Really it is good information.

    ReplyDelete
    Replies
    1. Saurav DhyaniApril 28, 2021 at 11:01 AM

      Great to hear that you liked the article.
      Thanks,
      Saurav Dhyani

      Delete

Post a Comment

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------
10 comments
Read Complete Article »

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.
Post a Comment
Read Complete Article »

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.
1 comment
Read Complete Article »