MenuSuite in 4.00

ngebhard

Hi everybody,

I am creating a new menusuite for a customer after upgrading from 3.70. We were using the table view option in version 370 and I don't know how to use this feature in version 400.

For example:
in 370 we were opening the customer card with a filter (for example country code=D). In 370, we just entered the runformview option in the command button on the menu. The entry there was "WHERE(Country code=FILTER('D'))". This saved a couple of new forms because we were able to use the standard customer form.

How can I do that in version 400? I don't see any properties to set! Did I miss it? Or do I need to create extra forms and set the filter in the form?

Any hints?!
Thanks a lot.

Best regards.
N. Gebhard

Marije_Brummel

As far as I am informed there are no real solutions for this problem.

Only workaround options are

1. Create different forms with different tableviews

2. Create a codeunit which calles the form with a filter

3. Start a 3.70 menu from the navigation pane.

If anyone knows other workarounds, let me know please,

greetz,

Marq

Timo_Lässer

In fact that you can't use C/AL Code in the Navigation Pane, there exists no real solution for this.

I think this filter will only appear for specific users. Some users should see all customers or customer from GB, ...
Another workaround (or possibly a solution for your case) could be:
Put a new field "Country Code Filter" in the table "User Setup".
In the customer card in the trigger OnOpenForm get this value and apply this to the customer records.

Customer Card - OnOpenForm()
IF UserSetup.GET(USERID) THEN
  IF UserSetup."Country Code Filter" <> '' THEN
    SETFILTER("Country Code",UserSetup."Country Code Filter");

ngebhard

Hi again!

By the reason that we have a couple of users which are supposed more than one option the workaround is not usable. The customer card was just an example, we use it with orders as well. We have different categories of orders which should show up in different menus and some user use all of them.

If I found out something new I will let you know. Maybe I try the codeunit hint. Otherwise I just created own forms.

Thanks!

N. Gebhard

Quasimodo

Hi,

well I just know this theoretically, means I have just read that such problems might get solved by the feature: "Responisibility Center"?

Michael

ngebhard

I don't think that this would solve the problem. Or at least I have no idea how!

Since some user are supposed to have more than one option? Otherwise this would be a good help..

Marije_Brummel

The MenuSuite in 4.00 is one step towards role-based front-end.

Expect this to be much further developed in the future where you will be developping more role-based forms.

However it would be nice to be able to run a form with a pre-defined filter from a menu.

Maybe this is Microsofts way to force you to make different forms for different roles? 8)

ngebhard

Guess so!

But I will try the codeunit solution first. Seems to be a good idea to save forms..

ngebhard

I just tried to create a codeunit which I call from the menusuite. Since I tried to create different functions and call them from the menusuite I realized, that I can't call a certain function. But if I can't do so I can't combine the functionally in one codeunit.

Solution:
make a form for every option?!

(I think I need to buy some more forms first!!!! =D> )

Marije_Brummel

Thats right. You cannot call a specific codeunitfunction.

You can use codeunits if:

A) You have more free codeunits available in your license than free forms

You might not want to increase the number of forms for database management, e.g.: If the orriginal form contains a bug, you have to solve the bug in all forms you copied it to. If you call the same form from a codeunit you keep it simple. This also helps if you want to upgrade.

kine

And make different bugs in the different forms... :-)

I am sending it as suggestion to MS... you can add your vote to this...

http://www.microsoft.com/Businesssoluti ... 94dc5cc939

ngebhard

I opened a request at the Navision support.
Here is the answer:

"Unfortunately the new menu system doesn't let us to play with the properties we got in earlier versions. It is because the main focus of the developers was to make it work for the 4.00 release, but there were no more time to do such additional improvements. But I expect to have it in the next version.
The only way to I can suggest is to create small menu forms that you can open from the MenuSuit. And on this menu forms you can create controls (Command Buttons), that already has the desired property.

I know that this isn't the answer you really like to hear, but I hope you can accept this explanation."