Notifications
Announcements
No record found.
Hi folks
I am hoping to earn a Christmas bonus. I have concluded that my chances will improve if I create a multi-select tree lookup for ISV solution X. There are many resources on multi-select lookups using a grid. But I haven't found anything on trees.
Does anyone have a link, hint or example?
Thanks for your attention
I've used tree lookups, multi-selection lookups and multi-selection trees, but not a multi-selection lookup with a tree.
I guess you can implement something like SysLookupMultiSelectCtrl which will use another class instead of SysLookupMultiSelectGrid.
Nevertheless I would try to avoid this design. For instance, if you open a form by a button, you have much better control over it (e.g. for sizing) than when using a lookup. And I'm not a big fan of multi-selection lookups in general.
and..."Christmas bonus" ?
Lol hi boss. I guess we can discuss it in the next company meeting? I am thinking something in the direction of 450% ...
Martin - thanks for the reply. You mentioned you have built multi-selection trees. Is that difficult? I mean a multi-select grid is easy (the property is on the element designer), but I don't know where to start with a tree. I have looked at MS docs and then from there I looked at the tree used with SysConfiguration (which looks great - I'd love to build something like that). But it is exceedingly complex.
Ahhh I see there is a "Check Box" property on the FormTreeControl. So I guess it is not so difficult at all. I think I will take your advice and build a form. Thanks.
Yes, using the checkbox is the way.
You can find tutorial_Form_TreeControl in older versions of AX; it shows working with checkboxes, among other things (if I remember it correctly). Unfortunately it doesn't exist in D365FO anymore.
Martin I have further questions if you don't mind.
For context: I am building analysis logic on bank account transactions. The user needs to be able to select which accounts he/she wants to view. So I had the idea that the user must be able to select bank accounts, legal entities and bank groups. Which brought me to the multi-select tree lookup. For example the user can select AccountA from USMF, BankAccountGroupC from GBSI, AccountB & AccountC from USSI and the entire USRT. Thus the root nodes will be legal entities, sub nodes bank groups and then bank accounts.
Which pattern to use depends on how you decide to model the GUI. The tree control can be used in many patterns, including Dialog - Basic (with Toolbar and List subpattern used for the content group).
A useful resource may be mfp's How to use a FormTreeControl. It's very old, but I think that these classes didn't change too much.
Regarding memory, I'm in the same situation as everybody else. While I do remember quite a few things, the amount of information I meet every day is insane and it's impossible to keep track of everything. I sometimes look at my own code written a few months back and I would swear that I've never seen it before... :) The same it is with some parts of AX. I too spend lots of time trying to figure out things that I knew a few years back but didn't use recently.
One Christmas bonus coming up
I was also having the same requirement on product search based on multiple product category, I did it in the following way.
dynamicsax.tech.blog/.../
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 664 Most Valuable Professional
André Arnaud de Cal... 522 Super User 2025 Season 2
Sohaib Cheema 303 User Group Leader