Disable Show all function

Is it possible to disable show all function on my new form?

Supawan, I’m not 100% sure I know what you’re asking?!?!?! [?] Do you mean, removing the Show Column functionality? ie: On the Sales Order Subform (Form 46), you don’t want to allow the user to select the Show Column by right clicking and selecting Show Column or by going to the View pull-down menu and selecting Show Column?!?!? In this instance, the only way would be to make the subform control on Sales Order form (Form 42), not ‘Focusable’. This may not be what you’re asking - sorry. [:)]

Hi Connull

quote:


Originally posted by CMDunbar
… In this instance, the only way would be to make the subform control on Sales Order form (Form 42), not ‘Focusable’. …


[}:)]! How should the user input or change data [;)]? IMHO the best way is to limit the fields on the form if the user shouldn’t see all fields. Just place only these fields on the form whom the user should see. But: Perhaps he wants to disable the ‘Show All’ function from the symbol menu? bye André

Hi, If you mean that you want to set a filter on the form that the user shouldn’t be able to remove (Pressing Show All) you can set a user-non removable filter by using Filtergroup. For instance, set this code in OnOpenForm: Filtergroup := 2; setrange(“salesperson code”, ‘MYCODE’); Filtergroup := 0; Then the user cannot remove the filter in field Salesperson Code. Filtergroup 2 is for filters that user cannot change where 0 is changable. Best regards Daniel

Or you can set the RunFormView -property of the form. If you filter the record there the user can’t remove the filter. (and he doesn’t see the filter [;)]) bye André

I would suggest never use FILTERGROUP with number below 6 as these groups are used by Navision itself. Better to use group 10 for example and use system groups only when it’s very needed.

Andre, --------------------------------------------------------------------- ! How should the user input or change data ? --------------------------------------------------------------------- Absolutely agree with you! This is why I wasn’t sure I was interpreting Supawan’s request properly! [:p] I think Supawan needs to tell us exactly what he means by the show all function!

It’s work,Thank you very much.

Supawan, Has it worked? What was worked?

Connull, I think everything works fine for Supawan [:D]

I can’t see the RunFormView - Property. I have SourceTable, SourceTableView etc on the Form -Properties. But I just can’t see RunFormView. Am I in the right place ? Can anyone help me ? Thanks.

Hi

quote:


Originally posted by Navicons
I can’t see the RunFormView - Property. I have SourceTable, SourceTableView etc on the Form -Properties. But I just can’t see RunFormView. Am I in the right place ? Can anyone help me ? Thanks.


You can’t find it in the form properties. You will find it in the properties of the menu or button to open the form. There you can set Form Id / Form Filter and so on… For example: Form 335 (Inventory Menu) Click on the Item button, then go to the properties. There you will find RunObject=Form Item Card. In the property RunFormView you can set the filters. bye André

[:D] RunFormView property is set only when you run form with filters. For example, using SETTABLEVIEW function or for Button with RunObject action and RunFormView property set. SourceTableView is not the same as RunFormView.

Thanks André, Thanks Arthur. Have a good week-end.

Hi Athur

quote:


Originally posted by Arthur
[:D] RunFormView property is set only when you run form with filters. For example, using SETTABLEVIEW function or for Button with RunObject action and RunFormView property set. SourceTableView is not the same as RunFormView.


I guess Supawan wants to show a form with filters which shouldn’t be removable by the user. IMHO RunFormView is the best way to solve this. bye André bye André

Yes, if you don’t need to set filters on run-time. Then only way is to use FILTERGROUPs.

quote:


Originally posted by Arthur
Yes, if you don’t need to set filters on run-time. Then only way is to use FILTERGROUPs.


YEP. Have a nice weekend.[:)]

Arthur you wrote “I would suggest never use FILTERGROUP with number below 6 as these groups are used by Navision itself. Better to use group 10 for example and use system groups only when it’s very needed.” I use FILTERGROUP(2) to set a filter, that the user cannot alter, and then set FILTERGROUP(0); How do you mean this is harmful? As I am just an amateur, I could use an explanation. Pelle

I can’t write this code on Runformview “PlanshipDate” Filter = 010100D…calcdate(‘1M’,Today) .So I need to use FILTERGROUPs on run-time.

quote:


Originally posted by pelle How do you mean this is harmful? As I am just an amateur, I could use an explanation.


FIILTERGROUPs < 6 is used by system. Here’s what help says:


Number Name Description 1 Global Not used, but may be used in the future. 2 Form Used for the filtering actions that result from the SETTABLEVIEW function; from the SourceTableView property; and from the DataItemTableView property. 3 Exec Used for the filtering actions that result from the SubFormView and RunFormView properties. 4 Link Used for the filtering actions that result from the DataItemLink and SubFormLink properties. 5 Temp Not used, but may be used in the future.


And a little more: It is possible to use one of the internally used groups (system filter groups) from C/AL. If you do this, keep in mind that in this way, you will replace the filter that C/SIDE assumes is in this group. If, for example, you use FILTERGROUP 4 in a form, you will replace the filtering that is actually the result of applying the SubFormLink property. This could seriously alter the way forms and subforms interact.