Creating LedgerDimension from DefaultDimension in D365F&O

 

Its a very common requirement to create ledgerDimension, based on DefaultDimension. Generally we have a habit of hardcoding the dimension names, to get the resulting ledgerDimension value: ex --

 dimensionMap.insert('CostCenter', '0033501_036');
        
 dimensionMap.insert('Location', '2023GBG');
Where CostCenter, Location, Purpose, etc. are various financial dimensions.
But wouldn't it have been great, if we could generalize the code, so as to eliminate dimension names hardcodes, so that if tomorrow the client decides to include more dimensions, edit or remove some of them, we don't have to change our code?
This article can give you a very handy code to do the same. All you need to do is to call it correctly 😊

I have created a class separately: DimDimensionHelper.
The following method has been added:
public static Map getDimensionWiseDimensionValues_DefaultDimension(DimensionDefault _dimensionDefault)
    {
        Map dimMap = new Map(Types::String, Types::String);
        
        DEFAULTDIMENSIONVIEW defaultDimensionView;

        while select Name, DisplayValue from defaultDimensionView
            where defaultDimensionView.DefaultDimension == _dimensionDefault
        {
            dimMap.insert(defaultDimensionView.Name, defaultDimensionView.DisplayValue);
        }

        return dimMap;
    }
Here you are  passing the DefaultDimension as a parameter, and then looping through the DefaultDimensionView view, and loading up the dimension name and displayValue as key-value pairs in a map.

Next we will pass on this Map along with the main account to create the segmented entry structure: 

public static DimensionDynamicAccount getLedgerDimension(MainAccount    _mainAccount, Map _conData)
    {
        
        DimensionDynamicAccount ledgerRecId;
        DimensionAttribute      dimensionAttribute;
        DimensionAttributeValue dimensionAttributeValue;
        DimensionSetSegmentName DimensionSet;
        DimensionStorage        dimStorage;
        LedgerAccountContract   ledgerAccountContract = new LedgerAccountContract();
        DimensionAttributeValueContract ValueContract;
        List valueContracts = new List(Types::Class);
        dimensionAttributeValueCombination dimensionAttributeValueCombination;
        MapEnumerator           mapEnum = _conData.getEnumerator();
 
        
        while (mapEnum.moveNext())
        {
            
            dimensionAttribute = DimensionAttribute::findByLocalizedName(mapEnum.currentKey(),false, CompanyInfo::find().LanguageId);
 
            if(dimensionAttribute)
            {
                dimensionAttributeValue = DimensionAttributeValue::findByDimensionAttributeAndValue(dimensionAttribute, mapEnum.currentValue());
                if(dimensionAttributeValue)
                {
                    ValueContract = new DimensionAttributeValueContract();
                    ValueContract.parmName(dimensionAttribute.Name) ;
                    ValueContract.parmValue(dimensionAttributeValue.CachedDisplayValue);
                    valueContracts.addEnd(ValueContract);
                }
            }
        }
        ledgerAccountContract.parmMainAccount(_mainAccount.MainAccountId);
        ledgerAccountContract.parmValues(valueContracts);
        dimStorage = DimensionServiceProvider::buildDimensionStorageForLedgerAccount(LedgerAccountContract);
        dimensionAttributeValueCombination = DimensionAttributeValueCombination::find(dimStorage.save());
        ledgerRecId = dimensionAttributeValueCombination.RecId;
        return ledgerRecId;
    }
Here its essentially looping through the map's key-value pair, and getting each and every dimension name, searching in the hierarchy. If a match is found, its trying to search the associated value pair and then loading in a list called 'ValueContracts'. Rest is very simple -- as we all know -- using DimensionStorageProvider to create a the dimensionValueCombination recId, and then sending it back to calling code.
Summing it up, here is how, you can call the above methods:
Map dimension = DimDimensionHelper::getDimensionWiseDimensionValues_DefaultDimension(_dimensionDefault);
ledgerDimaccount = DimDimensionHelper::getLedgerDimension(mainAccount, dimension);
transJournal.LedgerDimension          = ledgerDimaccount;

Hope it helps 😊 

Comments

Post a Comment

Popular posts from this blog

Make your menu items visible on main menu, conditionally,, using this cool feature of D365FO

Image
  Wassup guys? I am sure you must have encountered this situation where you needed to display your menuItems, on main menu, based on some condition, haven't you? This was only possible by using config keys and flights. Things get a bit tricky,  when suppose you have a requirement like this: you need to make it dynamic, by introducing a toggle switch on a field on a paremeter form.  Suppose on Accounts Receivables Parameters >> You have a field called ' Show US customer '. You have a requirement that says when you turn on this toggle, then only the menuItem ' Input SSN details ', under AR module. This is now highly acheivable by leveraging subscription to 'SysMenuNavigationObjectFactory' class, simply by saying a. Create a new class USMenuItemsVisibilityManager b. Copy the following method, with proper documentation (don't change signature/anything else) [SubscribesTo(classstr(SysMenuNavigationObjectFactory), staticdelegatestr(SysMenuNavigationObjec...
Read more

X++ : mistakes which developers commit the most

Image
   The most important thing is to remember where and when to write the code. a. Developers have an inherent habit of writing erratic select statements: select * from custTable where custTable.AccountNum == <SomeValue> Where in essence we need to make use of optimized choice of fields in the select statement. b. Making use of 'continue' keywords: While select custTrans where <someConditions> { if (cusTTrans.CustGroup != mappingTable.CustGroup) { continue; } } 'Continue' statements are precisely a very unhygienic way of designing your code. The above statement could have been easily ornamented by using exists/not exists joins. Using Continue statements would eventually result in a high performance impact. Also select statements should be made punctuated with a 'firstonly' clause -- just not from best practise standpoint, but also from performance considerations. c. Writing nested loops: This is a common mistake that perha...
Read more

Are you still using macros? Be sure you read this.

Image
  You still use a lot of macros in your code, don't you? Of course you should: Macros, as per Microsoft,  are p recompiler directives are processed before the code is compiled. The directives declare and handle macros and their values. The directives are removed by the precompiler so that the X++ compiler never encounters them. The X++ compiler only sees the sequence of characters written into the X++ code by the directives. However macros, are not quite recomended by Microsoft. They are slow, they can be subsequently deorectaed at any later time.  The Macros are  actually  a type of classes, only that they are not instantiated and not need be defined as classes. Hence runtime garbage collection could be a huge issue, consquently (a class when gets out of scope, gets garbage-collected owing to the destructor classes of DOT net instrumentation classes). Summing up, macrros are a bit old way of writing code. Use static classes instead. public static class MyIdenti...
Read more