Set Visibility Conditions on Fields
Steven Harbold
Jon Darbyshire This would be a massive step in building out more "work app" conditions in SmartSuite. AirTable lets you do this in interfaces and helps a lot in regards to long or conditional work flows to not clutter up the record. For instance. We write contracts for new homes and several fields and inputs are conditional on where there is an outside sales agent, and many other factors.
Also, in our contract documents table, when you open that record, I only need to see the "Addendum Date" field when writing an addendum document type. I only need to see "Contract Exp Time" when writing the contract etc.
This is pretty extensive across our AirTable ERP that we are trying to convert to SmartSuite. If you'd like to hear more about how we could use this, I'd be happy to demo.
Benjamin ~ Identify Solutions
Jon Darbyshire I want to jump on this and say I would use this a lot if it was available.
Also sometimes in records being able to put the same property in two different sections would be use case that I would love to see play out.
When you show and hide sections... sometimes you are making that decision based on a stage a record is in. But there is a property you don't want to leave out of sections just to have it visible. Sometimes you want it in the section where the other relevant data is and you might want it in two sections.
Sorry if my wording is unclear here.
Vasken Bakalian
Jon Darbyshire I came to canny to create this request and found out Ara Bozadjian has already created.
I have a use case with a client where we need this (screenshot)
The "Reason to decline" field will be always displayed, whereas we need it only when the stage = declined.
Now thinking of placing that single field in a section by itself.
Hope this helps!
Ara Bozadjian
Vasken Bakalian ha yes, we have considered the 'single field section' approach too but will get chaotic so we are going to hold out and hope this comes into play soon. :)
Vasken Bakalian
Ara Bozadjian makes sense, in my case here I have 2 or 3 such fields, and it gets messy when you have a ton.
I now love the expanded records, and I'll have more suggestion and make sure I tag you to have a look )
Benjamin ~ Identify Solutions
Vasken Bakalian I have similar use cases on this.
Jon Darbyshire
Thank you for posting, Ara Bozadjian! I have a few more questions for you:
- Can you provide examples of the types of fields you would like to set visibility conditions on?
- How frequently would you use this feature if it were available?
- Are there any specific visibility conditions you have in mind for these fields?
Ara Bozadjian
Jon Darbyshire I guess something simple like a Form would work:
IF 'DOB' Field = empty
THEN hide Age Field
As I set up our work flow and Records I'm finding myself overwhelmed with information so trying to reduce the clutter.
At the moment, only way to hide a Field is to put it into a Section and Set Visibility Conditions for that.
P
Paul Stengel
Jon Darbyshire Checklists would be a great field to set visibility conditions. I would use this to allow users to then choose from a multi-select to set the conditions for a number of checklists to appear on a task. This way, users can create tasks quickly for common tasks with team defined checklists and support documents. This would help our team scale our PM best practices, essentially embedding SOP links into the checklists. I would use this everyday. Currently planning to set up a bunch of sections with a single check list which is not ideal but works for now.
Jon Darbyshire
Ara Bozadjian I agree that this would be useful and this is a feature that I have implemented in a product at a prior company I founded. The issue I am trying to figure out relates to page display performance as this brings lots of overhead when customers have records with over 400 fields and also have lots of rules like this. I will move this up in the my of things to time about and try to find an optimal way to manage this.