Individual User Menus - Census of opinion ???

Until recentley, if a site required their users to have customised menus ( i.e. hide buttons etc) then I would have created a new menu form. In other peoples experiences, in what ways would you deal with this and what has been found to be the best solution ?

I think you are on the right track. In most cases specialzed menus are the right choice. They are also much easier to maintain than menus with complicated “SetVisible” logic. ------- With best regards from Switzerland Marcus Fabian

Thanks Marcus, This is the solution that I used to use. Does anyone have any other solutions to this ?

My opinion on this issue: Creating customized menus for each user group is sooner or later gonna be a mess! We have a routine, that allows you to export the main menu form 330, as text, run it through the routine, and voila it has named all the buttons on the menu, and inserted code to keep track of visible / non visible. This is controlled by a setup table. Further more for the US version it has this for each subform, and change/log functionality for every table. Of course this solution will be more expensive, because of the use of tables for storing the setup, but the advantages is much greater than the cost. Soren Nielsen, moderator Integration/Developer NOLUG

We use the visible true/false route. In the User Setup Table we assign each user a security level (0 to 100). The control is visible if their security level is greater than the control’s level. You cannot mix or match the security, but it works for the most part for us. Michael

Visible True/False is untidy compared to new menus ,gaps between the buttons and you can’t restrict the navigation to other areas,so you have work to do in permissions any way ,maybe Navision could give us user dynamic menu’s one day! I leave the Main Menu’s alone for consistancy and use table permissions to restrict access, Navision is an open system that’s one of it strong selling points! David Cox MindSource (UK) Limited Navision Solutions Partner Email: Web:

In an ideal world, the way in which David has described would be perfect (not doing any customisation), but I do not seem to live there. End-users can ( and usually do) want these modifications to be made.So, this leads me towards agreeing with the way in which Soren deals with the problem. I do agree with David on the way in which this makes Navision look, it would be very “unpretty”, but, what if this could be done ? Would it be worthwhile to spend the time developing this ? Would this be the Dynamic Menus principle that David is talking about ?

Just another point about hiding menu buttons. I belive in letting the end use see what navision has to offer, one departments needs may be the main focus of an installation and cause potential product sales being missed. I had the situation in the past where button’s were hidden to streamline the menu’s, which were in user groups ie: about 4 different main menu’s with buttons switched off. when in discussion’s a head of department was talking about how to move forward by buying different software to interact with Navision, because Navision has “No Contact Management or Jobs Capacity” which had been hidden by the developer. The user’s had no permissions for these menus so why hide them? If all the end users can see all menu options, someone may ask if a granule in Navision will suit there departmental needs, if they don’t know it exist’s they won’t! The cost of hiding buttons can be financial as well as time wasting. David Cox MindSource (UK) Limited Navision Solutions Partner Email: Web:

Very good point David, I had not really looked at it from that angle. I did however, look at it from the managers point of view, in which they usually have full access to everything, therefore I would never hide buttons for these types of users. Thus, if they saw these buttons, then (as you rightly pointed out)these managers would actually know about the additional modules that are avaliable. This has provided food for thought. Many Thanks to all !