Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Disable (enabled false) of a sub button in dropdown button
nXqd
Member Posts: 39
hi,
I have a form which contains a dropdown button. I want to know how to disabled sub buttons that belong to the dropdown button at the run time, can I do it ?
I've tried CurrForm.DropbownButton.Button but it doesn't work.
I can archive the same effect of disabling the buttons by checking conditions when user clicks on it, but I just want a fancy effect of gray out button
Thanks,
I have a form which contains a dropdown button. I want to know how to disabled sub buttons that belong to the dropdown button at the run time, can I do it ?
I've tried CurrForm.DropbownButton.Button but it doesn't work.
I can archive the same effect of disabling the buttons by checking conditions when user clicks on it, but I just want a fancy effect of gray out button
Thanks,
0
Comments
A workaround is to create 2 Menubuttons on top of each other and by some condition hide one of them.
FD Consulting
True Franky (how is life in Hamburg?), but I didn't want to even point in this direction since if anyone ever looks at the form afterwards and don't know you'll end up with questions.
If you do this, then at least put it in the documentation in CAPS and use functions for each menuoption. The latter is general best practice.