Menu Suite

icouto

Hi,
I have a Form that is to be open in two different Menu Items (on Menu Suite), and I would like to filter which data is shown.

For example:
Menu Item 1 -> shows data type A
Menu Item 2 -> shows data type B

Is this possible? How?

Regards,
Ivo Couto.

HalMdy

I think you can not put a specific filter on the call of the form in the Menu Suite ...

Proposal :
- duplicate your form with right filter
- create two Codeunits that call the form with the filter and call the Codeunits from the MenuSuite.
- ... ?

icouto

Thanks HalMdy.
I have already thought that, but I am trying to find a less expensive solution. My license doesn't many forms or codeunits left.

Ivo Couto.

Timo_Lässer

HalMdy wrote:

[...]
- create two Codeunits that call the form with the filter and call the Codeunits from the MenuSuite.
[...]

Why two codeunits? You only need one because you can call the form without parameters :-$
(just my 2 cent)

Waldo

Because he needs to call the form in two places, in two ways...

I have a Form that is to be open in two different Menu Items (on Menu Suite), and I would like to filter which data is shown

Timo_Lässer

You forgot that you can run a form without parameter and so the form shows the data in variant A.
If he wants to start other than variant A then he needs a codeunit which calls the form with variant B and another codeunit which calls the form with variant C and another ...

Yes, I know that you can only save one codeunit but every object costs money.

POOL_DSFT

You can duplicate the form and apply to each one the filter that you want

Waldo

You forgot that you can run a form without parameter and so the form shows the data in variant A.
If he wants to start other than variant A then he needs a codeunit which calls the form with variant B and another codeunit which calls the form with variant C and another ...

Yes, I know that you can only save one codeunit but every object costs money.

Ah, now I see what you mean ... sorry ... ](*,)

Timo_Lässer

But the easiest (and imho best) way is to create several forms (as already mentioned by POOL_DSFT and HalMdy).

fb

And the least expensive way is to put the following code in the OnOpenForm trigger:

intChoice := STRMENU('Option 1,Option 2');
CASE intChoice OF
  0: CurrForm.CLOSE;
  1: SETFILTER(myFieldx,'Option 1');
  2: SETFILTER(myFieldx,'Option 2');
END;

Timo_Lässer

#-o ](*,) =D>
I don't see the wood for the trees.

HalMdy

Timo : fully agreed with your Forms-base solution.

fd : yep, but with that you don't manage the choice from the Menu Suite as asked ... :-k

Meaby our Navision friends could take this proposal for next release : opportunity to put filters in the calls from Menu Suite ...

Waldo

hm, (imho) I prefer the Codeunit-solution. I'll tell you why ... .

When (in a near or far future) the form is altered by adding some functionality ... adding some menu-items and so on ... then this should be done in 2 forms [-X . All modifications should be done twice. :-k

OK, doing this with two seperate forms, it's a less expensive solution, but "less expensive" doesn't mean "better solution". For me, it's less maintainable.

again, this is only my opinion.

Timo_Lässer

fb's solutions needs only one form, no codeunits and a minor coding in one trigger.

Waldo

Yes, OK, but then, every time you open the form, the user has to choose which filters has to be applied. You really think the users wants to click that option every time.

Also ...

icouto had to create two menu items ... probably for two seperate types of users who have access to the seperate menus. Choosing filter each time they open the same form ... this is not really user-friendly, is it???

kine

Waldo wrote:

When (in a near or far future) the form is altered by adding some functionality ... adding some menu-items and so on ... then this should be done in 2 forms [-X . All modifications should be done twice. :-k

You can go around this by doing the second form something as wrapper form - only run the first form with another filters... and after closing this called form, close itself too... (and you will have form icon in the MenuSuite, not codeunit icon)...

Shenpen

I think the STRMENU solution is really bad, because it allows the user choose the option he is not supposed to choose, because it is not relevant to his job responsibility. Generally, the surest way to doom a project is to only make functions users allow to do what they need to do. The biggest and more important part is to take away everything from the they are don't need or allowed to do. Both for security reasons and to be fool-safe.

I'd vote the 2-form solution. No, it is not unmaintainable: the two forms will soon fork and in 3 months they surely will not even resemble each other. Maybe the first is called Something for Salespeople and the second one is called Something for Warehouse People - you can bet in 3 month they will be totally different.

If you want to make a good project, this approach is unavoidable - to make stuff like Customer Card for Salespeople, Customer Card for Managers etc.