Hide browse columns in runtime

[Nick]

Is this done? I often been asked for by users to put more fields in browses. More than other users want to see or
can show on their screens.
With mobile stuff this really seems important.
 
It seems possible:
A column is clickable and the column ID can be passed,
What's needed I guess is a procedure that knows the browse and the columnID and stores
this with a show/not show value.
Is this something for a template option?

Nick

[Stu]

Hi Nick,

Not entirely clear what you're asking .. But.

If you want a checkbox that hides/shows fields, then:

BYTE field
- Add as a checkbox to the browse.
- Make sure it refreshes the whole row / browse.
- Then on the fields you want to show/hide, put the check into the Column Condition template field. IE

Code: [Select]

prefix:fieldname=1

[Bruce]

Hi Nick,

there are 2 settings for the browse column which you can use here;

a) Column Condition:
put any condition in here you like. If it evaluates to false then the column is excluded.

b) Include In Mobile?
tick this on to include, or off to exclude, this column when the app is in "mobile mode".

cheers
Bruce

[Nick]

>>If you want a checkbox that hides/shows fields, then:

>>BYTE field
>>- Add as a checkbox to the browse.
>>- Make sure it refreshes the whole row / browse.
>>- Then on the fields you want to show/hide, put the check into the Column Condition template field. IE

Yes I thought of that too but that would mean that you need a checkbox for every column because how else
do you know which column to hide?
Apart from that it should be saved so that the user doesn't have to do this again and again.
I thought of making the column itself clickable so you don't need the checkboxes.
It takes no extra space and by clicking on a column you know which column to hide,

Thanks.
Nick

[Nick]

Hm.. a clickable column that is hidden can't be clicked again... 
I think we need a table that must be constructed on the fly containing column-names with
checkboxes to switch each column on/off.
Then there is the multiple user problem. May user A hides a colum so that user B can't see it too?
Sessionid's don't help here if you don't want to hide the columns for every session.
So it should be coupled to a user login or this system could be protected so that only a restricted
number of users can hide/unhide columns. Then sensitive info like prices etc. could be hidden to
some users.

Nick

[kevin plummer]

Hi Nick,

for system security I use a separate table to store the choices the admin makes or you could use sec win.

for user choices, I tend to use a popup or setup form and save the details in an ini file with their login

Kev

[Bruce]

Sounds like you wan to use Secwin Nick.
That has column-level security as a feature.

cheers
Bruce

[Nick]

Hi Bruce,

Hm.. I have Secwin and am still waiting for your answers to a few problems I mailed you last week.

Didn't know SecWin could do this. So Secwin can hide columns for those users who are not alowed not see them?
Ok, that's part of what I want but I also want to hide columns just because they won't fit on a particular screen
or because I just don't want/need to see them. Probably I can fiddle a bit with Sewcin to acomplish that too...?

Thanks.
Nick

[Bruce]

>> Hm.. I have Secwin and am still waiting for your answers to a few problems I mailed you last week.

yes - they're in the queue.

>> Didn't know SecWin could do this. So Secwin can hide columns for those users who are not allowed not see them?

correct.

>> Ok, that's part of what I want but I also want to hide columns just because they won't fit on a particular screen

hence the Column Condition I mentioned earlier.

they're two separate problems, with two separate solutions.

cheers
Bruce