Disable Navigation Pane

Frikolino

Hi,
we have jet installed Navison 4.02. Now I want to create some simple Form-menus (like 3.70), but after login I will allways get the Navigation Pane too.
How can I disable the Navigation-Pane permanently?
(ALT+F1 is not enough)

kriki

You can try NOT to give Navision permissions on the menusuite-objects.
And when you hide the menusuite, this fact is saved in the zup-file. So you might create a zupfile with the menusuite hidden and copy this for the new users.

MissesMagic

kriki wrote:

You can try NOT to give Navision permissions on the menusuite-objects.

I don´t think this is possible! First thing Navision does is opening Pane. If you don´t have permission - you can´t work. And I still haven´t found a way to do other
(If you find one - please give me the answer)

kriki

You can use sendkey to simulate keyboard input to close the menusuite. (see automation Windows Script Host Object Model'.WshShell)

kine

kriki wrote:

You can use sendkey to simulate keyboard input to close the menusuite. (see automation Windows Script Host Object Model'.WshShell)

Yes, but how to detect, if the menusuite is hidden or not??? ;-)

kriki

kine wrote:

kriki wrote:

You can use sendkey to simulate keyboard input to close the menusuite. (see automation Windows Script Host Object Model'.WshShell)

Yes, but how to detect, if the menusuite is hidden or not??? ;-)

Right :oops:

fl

Hi,

There is a solution for this problem if you never want to use a manusuite in your nav4. The menusuite is started by the trigger used in the procedure companyopen in codeunit 1. (Already mentioned several times on this forum)

In 370 you can see:
PROCEDURE CompanyOpen@1() : Integer;
VAR
UserSetup@1000 : Record 91;
MainMenuID@1001 : Integer;
BEGIN
IF USERID <> '' THEN
IF UserSetup.GET(USERID) THEN
MainMenuID := UserSetup."Main Menu ID";

IF MainMenuID = 0 THEN
MainMenuID := FORM::"Main Menu";

In 400 you can see:
PROCEDURE CompanyOpen@30();
BEGIN
IF GUIALLOWED THEN
LogInStart;

The difference there is the trigger used in both routines. 370 uses 1 and 400 uses 30. If you change this trigger to 1 in version 400, then no navigationpane will open. Of course you have to add code to start your main-menu. The trigger can only be changed in a exported text object, as far as i know, which can then be imported again.

However, this solution is only OK if all the users of all the companies of a database need to start the same type of menu: or navigation pane or main menu.

Frikolino

Thanks for your replies, but if I try to change CU1 (txt export-import) I got an error:
"The function ID 1 is used by both function CompanyOpen and function UserOpen".

kriki

This means you already have a function that uses ID 1. This function is called when you press F12 or click on the menubutton on the right of the screen (and not used anymore by 4.00).
So you have to add your code in the existing function.

fl

Strange, I did try this some time ago, and it worked at that moment. I looked in the CU1, but couldn't find there any procedure UserOpen. Is this some modification ?

Frikolino

sorry guys, I think I'm a little bit stupid, so I must answer again ;-)
I have deleted the UserOpen-Proc and renamed then CompanyOpen-Proc:

PROCEDURE CompanyOpen@1();
VAR
..
BEGIN
IF GUIALLOWED THEN begin
LogInStart;
end;

Import works fine, but after a restart the Pane opens again. Where must I insert some Code?
Isn't it possible to prog. something like in CU1 in 370 (default: the Pane or a User-Form from User-Setup)

fl

Did you try to import CU1 from 3.&) in the 4.00 version. But watch the other changements in this CU.

kriki

Frikolino wrote:

Import works fine, but after a restart the Pane opens again. Where must I insert some Code?

That is strange. Are you sure you are using the same zup-file as before the restart?
The fact that on startup the pane is open or not is saved in the zup-file.

Frikolino

hi again,
i am very confused: I have import the complete CU1 from 370 into 400. It works after some compile-errors. But the navigation-pane opens again.
After that I completely deleted CU1 (!) and the pane opens again.

How is that possible? Where is the switch to kill that fu**ing Navi-Pane. I only want my old 370-Menus ;-)

themave

I know this is not what you want. but just learn to use the menu suite, We thought we had to keep the old menu's but didn't want to pay to program the change, so we never told the users we were considering going back to the old structure, everyone adjusted very fast,

the shortcut menu is the most used thing now.

I created a company wide menu and everyone just creates there own short cuts for the things they use most. It is actual much better then the old menus.

kine

You need to not forget to delete the zup file. If you open the menusuite once, it will be saved in the zup file and the menu suite will be open next time...

Albertvh

from some documentation that I have

Opening a Company in Navision 4.0 with a Specific Form Shown

If you want a specific form to be launched when users open a company, you have to create a trigger with ID 1 in Codeunit 1 with code that corresponds to the CompanyOpen trigger code in earlier database versions. To enable user-specific forms to be launched, you must enter User IDs and Main Menu IDs in the User Setup table. Please note that you may have to insert the “Main Menu ID” field in this table first. You can still run the Navigation Pane if required.

weis_guys

Okay, this works.
1) Export Codeunit1 from 3.70 and 4.00 to text. Cut the 370 CompanyOpen procedure and paste it into 4.00, replacing the existing one.
2) Import the modified 4.00 codeunit back in. Change the properties of the Global Functions LogInStart and LogInEnd from local Yes back to the default of No (the Main Menu uses them).
3) Add the Main Menu ID Field to the User Setup Table.
At this point you have both the old menus and the Navigation Pane, working. Those who don't want the Navigation Pane, turn it off and the zup will remember to leave it off.
This gives you the best of both worlds and allows for an easier transition.

You will no doubt need to resolve specific form conflicts by testing each old menu selection of modify the menu as needed. \:D/