Kinetic Configurator – Is It Possible to Hide a Column?

Hey folks,

I’m working on a Kinetic Configurator layout in Application Studio and trying to conditionally hide one of the Column controls (the layout item from the toolbox, not a grid column).

My use case:

  • I have a row with five columns in it. (See screenshot)
  • Based on a user selection, I want to hide one or more of those Columns.
  • I’ve given each column an ID Name and used Data Rules to try and set them to invisible.

But… no luck. They remain visible regardless of the rule.

What I’ve tried:

  • Using a Data Rule to toggle visibility (e.g. setting the Column’s Visible property to false).

  • Looked for a way to do this manually (not found one)

So now I’m wondering:

  • Is it even possible to hide a Column?
  • If not, what’s a good workaround to achieve the same effect?
  • Is there any trick to structuring layouts when visibility needs to change based on user interaction?

I’m still fairly new to Kinetic Configurators, so all advice — even the obvious stuff — is very welcome!

Thanks in advance! :raised_hands:

2 Likes

Josh,
I’m curious about this behaviour as well. If you hide all the inputs in the relevant column (a pain, but possible), I believe you’ll achieve the same effect.

We’ve been using panel cards hide/show relevant inputs when they are opened / collapsed. It’s a vertical layout rather than horizontal, so it’s a different perspective on the flow. Rather than left-to-right, the inputs flow top-to-bottom. The Kinetic configurator is a fly-out from the side of the screen so this vertical layout fits that aspect ratio.

P.S. we’ve never used a panel card stack but it’s on our list of things to test to improve the layouts.

Hi @aball,

Thanks for replying!

I’ve just tried this and it worked to a degree. It isn’t actually what I wanted though

See screenshot the boxes obviously disappear, but the header remains with the gap. I was hoping for something that would just display the screen with only 4 columns.

But I appreciate the response, might trigger another thought for someone of how we could work this out!

What happens if you delete the header?

If that works, you could change the headers to labels and put them in their own Columns above the inputs. Then hide/show them in coordination with the inputs.

This feels like a Rube Goldberg solution but it might work.

1 Like

Hi @aball,

It looks better that way I think (No Header, but with label). I think a user would be less inclined to think something just hasn’t loaded yet.

It’s not exactly what I wanted as the label isn’t as clear as the header but it’ll do for now. I might put an idea suggestion on though so we could hide a column feels like that would be quite a useful thing…

Idea for reference…
https://epicor.ideas.aha.io/ideas/KIN-I-6391