Hi everyone,
I often use the toolbar item that lets a user add or take away columns form a grid. Has anyone found a way to save the user’s selection of columns and reapply it at a later visit to that grid?
Thanks,
Jamie
Save Grid - seems to do what I wanted
Looks like user would have to click Save Grid button and apply a particular column layout they saved previously.
I am now in version 9.2.0000
I learned something about Save Grid today. The documentation is very skimpy on this in Help. You have 2 settings you can check. One is Enable Public , and second is Use Rules.
- One of those options has to be checked of the entire Save Grid button disappears from toolbar.
- Both can be checked.
- If you check Enable Public, then when a user saves a grid layout, they can save it to a public “area” where other users can access and use it. I believe any other user can also delete these as well. I guess in certain applications this could be a good thing, but with the number of users I have the list would simply grow too long and confusing to the users.
- Use Rules. This is very confusing in the documentation IMHO. You can add a new rule - giving it a name, label, and a variable. The name seems to be an internal thing. The label is what the user sees as an option. The variable became useful to me as follows:
I added a rule with:
Name: usersaves
Label: My Saved Layouts
Variable: [usr_login]
When I do this, every user seems to be able to pick this ‘My Saved Layouts’ and then they do not see each other’s saved layouts. The global variable I put in [usr_login] is coming from their specific authentication in sec_Login. I was able to login as 2 different users and each could save layouts and not see the others.
If you had a team value stored in a global, like [my_team_id] or something, that was common to multiple users, then you could add a rule here that each team member could access for saving. I tested this as well. Both rules are then available as a drop down to the users. Note, any saved layouts that can be seen by multiple users can also be deleted by any of them as well (just like Public Enabled). But in this case, my user teams are very small and they talk to each other so they can us this as a useful feature!
Anyway, thought I would share this so far
Jamie