Allow Users to Select Displayed Columns in Grid View

[kukuk52]

It would be great if the KTL would allow users to select the columns that they'd like to display in a given grid (much like you've done with the grid filters). Saving your preferred column selection locally would allow quick access to displays of preferred data depending on the project the user is working on. Ideally, this would also apply when exporting that grid (although I realize that's a much heavier lift).

[cortexrd]

Hi Daniel,

Thanks for suggesting this feature. I've brainstormed on it lately and I think I have a good idea how I'd do this.

To prevent conflicting with the User/Public Filters' real-estate, I think I'd use a drop-down or a pop-up window to select the "Layout" instead of horizontal buttons like filters. Since column toggling is not a feature you'd use 20 times a day most likely, that would be acceptable.

So you'd have new a "Hide/Show Columns" button that, when clicked, would...

1. open a dropdown or pop-up, where you'd see Save, Delete, Rename, Layout1, Layout2, etc.
2. add an eye icon (button) on each column, that would be green or red (for show/hide). When the eye icon is clicked, it would toggle the column's visibility.
3. The layouts would be saved, per application, user and view. They would be saved in localStorage for persistence.

But the export to CSV only for the visible columns... that's another story indeed. That would require re-writing the export, with page flipping when data is more than 1000 records.

Any other ideas?

Norm

[kukuk52]

Norm, this all sounds really great. I agree, a dropdown or pop-up would keep the page clean and allow the users to select and save their preferred views. I know this may be a bit more complicated, but have you considered universal preset column configurations (a developer or user admin could set up some specific views that users would have available on their end)?

While the export function would really bring this together, I don't think it's something that should prevent or slow the development of this tool.

Thanks again.

[kukuk52]

Hey Norm,
Have you further considered implementing this feature? If so, when would you think it might be available? Thanks!

[cortexrd]

Hi Dan,

Yes that feature (call it a project) is still very much in the scope, and quite desirable. Many people have asked for it actually, along with the Excel/CSV export based on visible columns only.

I have no time at the moment, being super busy with my main client's projects. But I may have a contributor that could help me on this - let me check.

Norm

[cortexrd]

Hi Dan,

I've completed a part of the feature. You can hide/show columns but not save the settings for now.

You can try it out to see a preview. It's not officially released yet, so you need to set the version to dev in the loader, like this:

KnackInitAsync = function ($, callback) { // Load the Knack Toolkit Library (KTL)
    (window.LazyLoad = LazyLoad) && LazyLoad.js(['https://ctrnd.s3.amazonaws.com/Lib/KTL/KTL_Start.js'], () => {
        loadKtl($, callback, (typeof KnackApp === 'function' ? KnackApp : null), 'dev' /*KTL version, leave blank to get latest*/, 'full'/*min or full*/);
    })
};

Then do a Ctrl+F5 to force an update, bypassing the cache.

You will see a pale left-pointing caret (arrow) in each column header. When you click on it, the columns is collapsed to 20 pixels and show with a hatching. Click anywhere in the column to expand it back to normal.

Let me know if you like it,
Norm

[cortexrd]

Hi Dan,

Any feedback on the _hsc keyword?
It's now in official release v0.18.8.

Norm

[kukuk52]

Hi Norm,

This is a great start and a useful tool that I'll be adding to a few of my grid views. That being said, I'd still really like to see something more like you described above where there would be a pop-up that would allow the user to select what columns they'd like to show/hide. To really make this useful, I think the selection needs to be saved with the logged-in user or on the local storage so that someone doesn't have to re-filter their view every time they navigate away from the page. A default selection would also be great if possible.

I've been thinking through some workarounds to accomplish this, but to have it built right into the KTL would be amazing.

Thanks again for all you're doing!

[kukuk52]

Would it be possible to use the _hc keyword and some conditions to make this work? If the user updated a record with a multi-select multiple choice field that contained the names of all the fields that were available to show/hide in a given grid could that be used as a reference to show/hide the various columns?

[CSWinnall]

I think that's a good idea and might be possible if you had a separate _hc for each column you want to hide and use ktlCond with the contains operator. Yes I think this could work. The field with the list of columns could be in details view with an edit form the user could add or remove columns.

I will have to give this a go and get back to you.

Great idea.

Craig

[CSWinnall]

You could have a grid, in each row a name of a column and have a yes/no field and use the quick toggle keyword so the user could quickly toggle the columns on or off.

[cortexrd]

Indeed, very clever! You're using the KTL in ways I didn't even think of myself LOL!
That should work for sure, with Details view that has the checkboxes of columns to show, and several _hc in the grid, with ktlCond.

Norm

[kukuk52]

That's a pretty neat idea. What would the keyword input look like on the main grid (the one where we'd want to show/hide columns) to get this to work?

…

On Tue, Dec 5, 2023 at 3:38 PM CSWinnall ***@***.***> wrote: You could have a grid, in each row a name of a column and have a yes/no field and use the quick toggle keyword so the user could quickly toggle the columns on or off. — Reply to this email directly, view it on GitHub <#45 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANQJOGOONPHUFLHSPCYUUN3YH6A6FAVCNFSM6AAAAAAY7YEVL2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TONRYHAYDM> . You are receiving this because you authored the thread.Message ID: <cortexrd/Knack-Toolkit-Library/repo-discussions/45/comments/7768806@ github.com>

-- Daniel J. Kukuk Data & Communications: AFT Michigan, AFL-CIO ***@***.*** (248) 894-9899

[CSWinnall]

Sorry In a bit of a rush but I tried this and it worked fine :

_hc=[Client], [ktlCond,has, Client, field_540, view_212]
_hc=[Sex], [ktlCond,has, Sex, field_540, view_212]

Craig

[CSWinnall]

I can't see anything wrong or different with your _hc keywords apart from using the field id if that's the case there may be an issue with using field labels in ktlCond @cortexrd.

Let us know if that fixes it.

[kukuk52]

Yes, I was thinking of this backward (showing vs hiding). This seems to be working now! Is there a way to run the inverse of this (ie: does not contain) so that the displayed fields would be those that are selected? This just seems to be more intuitive from the user side. I'm sure we can run with this solution if that's not a possibility.

[CSWinnall]

Unfortunately I do not think that this is possible if you have all the options in one field. There is not an option for has not or doesn't contain.

You could possibly do it if the _hc ktlCond pointed to a different field that you update with record rules depending on which options are selected not selected.
e.g. if Someone selects Email in Viewable Fields to show you then remove it from the other field Hidden Fields and vice versa.

Craig

[CSWinnall]

Yes this is doable:

Here are example keywords:

_hc=[Client], [ktlCond,has, Client, field_541, view_212]
_hc=[Sex], [ktlCond,has, Sex, field_541, view_212]
_hc=[Contact], [ktlCond,has, Contact, field_541, view_212]

Here are example record rules in your edit form:

Add 2 fields into Account

If you have a lot of fields, then this could get long but it works.

Craig

[CSWinnall]

@cortexrd is there a way to not- conditions in the ktlCond?

Like !has

[cortexrd]

Yes, I have implement this a minute ago.
It will be hasnt.
I need to test it, and it should be in next release.

Norm