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

 


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(SysMenuNavigationObjectFactory, checkAddSubMenuDelegate)), Hookable(false)]

    internal static void menuItemVisibilityHandler(SysDictMenu _rootMenu, SysDictMenu _subMenu, SysBoxedBoolean _subMenuVisibility)

c. And then just introduce the following code in the method:

if (_subMenu.isMenuItem())

        {

            var metaElement = _subMenu.GetMenuItemMetaElement();

            if (metaElement != null)

            {

                vendParameters parmTable =  VendParameters::find();

                switch (metaElement.Name)

                {

                    case menuItemDisplayStr(SHOWSSNCustInputTable): //give the name of your menu item here                   

                        _subMenuVisibility.value = pamrTable.DXCCustomerSKUOnHold == NoYes::Yes;

                        break;

                }

            }

        }

Change the name of the menu item here, as you need. When you save the code and get back to Vend parameters table, and change the toggle to No, and reload your application page, the menu item is gone!

Yes, this cool hack can help you manipulate the visibility of your application's menu items, as you need.

So much for today, see you soon again with another blog 💓💓💓 


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

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