Year wise data for faster execution, in D365FO, using Views

 

You must have bumped across a situation in your implementation career, where you needed to class your data, based on year. As an example:


It becomes very difficult to design such a structure, where individually you might need to write code for every customer, for each year:

select sum(AmountMST) from custTable

where custTable.TransDate >= fromDate

&& custTable.TransDate <= toDate;

It will eventually result in extreme slowness of the process, which will make it go through each and every customer, over and over for all customers, for all the years.

Definitely not a good solution.

In all such cases, we can make a solution like this:

a. Pre-calculating the year as 'Year-names' in a view, where we can store the years like 2021, 2022, 2023, (no hardcoding):

Here 'YearName' is a computed column, which looks like this:

private static server str compYearName()

    {

        

        #define.PPCustTransYearNameView(PPCustTransYearNameView)

        #define.DataSource(CustTrans)

        #define.RecIdField(RecId)


        str yrExp;

        yrExp = 'select Year(TransDate) from custTrans where RecId = ' +

                    SysComputedColumn::returnField(

                                                    tableStr(#PPCustTransYearNameView),

                                                    identifierStr(#DataSource),

                                                    fieldStr(#DataSource, #RecIdField)

                                                    );


        return yrExp;

    }

Look at the code: it just takes out the Year part of the TransDate field of CustTrans table. And then we are using it as a computed column.



b. Creating another view (which refers to this view)  so as to bucket up the balances into quanta of years:


Here we are referring to our previously created view and then using the YearName column and the AmounMST column (which is a sum column):


 
As a result the view gives the year wise balances as follows:


You could see clearly that it's giving you year wise balances for every customer.

c. Calling the view, by passing on the customer and year: Now you can directly call this view, by passing on customer code and the year name. This will directly give you the output without even needing to calculate for every customer and resulting in unwanted slowness.  

Where you can use this:

1. Year wise customer sales related processes, reports, 

2. Customer trend.

3. Advanced analytics, etc.

Comments

Post a Comment

Popular posts from this blog

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

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

Speed up your execution performance by using SysGlobalCaches

Image
  Ever come across a situation where you needed to  a. Using a multi-threaded batch to import a journal header and lines, from a staging table. The table already contains the Journal Ids which you need to assign to the header and allocate the lines under that header. b. You need to continuously check after each line being imported, if the journal with the Id has been created. If not, it will create the header and create the lines under it;  If yes, it will directly create the lines for the header (Find or create). c. As you could rightly guess, this architecture has an inherent sluggishness associated with it -- each time you keep on checking if the header has been created or not, it does mean a lot of performance effects, as a consequence. Also as you can understand it's a multithreaded code, which means each thread has no direct relation with the other -- which does mean there is no way I can talk between the threads/pass on any information. SysGlobalCaches to the rescue: I perso
Read more