I’ve been slowly adding more advanced formulas to my base and I’m starting to create formulas that have errors in them that I cannot find easily. I’m also a pretty heavy user of Cognito Forms and I really like the way they handle formulas with errors: The simple debugger lets me know the general vicinity of the error which allows me to understand what I may have done wrong. Usually the issue is a simple syntax issue, but with larger formulas with nested if statements which often contain additional functions, tracking down issues can be somewhat problematic. A little help in this area via a built-in tool would be much appreciated. ... View more

Would be a useful feature to minimise selection from a linked table’s rows. Example: Our business has subcontractors who become active and inactive at different periods, their activeness represented by a checkbox data column. If they are inactive, they should not be able to be selected when assigning a subcontractor to a service. ... View more

It would be useful to have a “Button” field type that you could use to trigger an action (e.g., perform a calculation, run a Block, trigger a Zapier Zap, run a script, run small automations, etc.). Even though some of this functionality can currently be hacked-together using other fields like checkboxes in conjunction with Views and Zaps, this is something that has to be explained ad nauseam to new users. So, instead of having a “Submit” checkbox in a workflow that can accidentally ticked, having a distinct “Submit” button would be much, much more clear to novice/infrequent users. This is a feature currently offered by Coda. help.coda.io Overview of Buttons Learn how buttons can create workflows and an app-like experience in your doc ... View more

As my list of ‘Views’ evolves, I am finding it frustrating that there is no way for a view to inherit the changes I make in another view. I would find it very helpful to create views in a hierarchy so that changes are inherited by the child view, but omitted (hidden) in the parent, if created in the child view… something like this: ... View more

When I am searching for a linked record, I can only search if I know the first field (locked) for that table. However, when I start typing, I can see other fields listed in the options for each record that comes up. I’d like to search by those other fields, that will still get me to that linked record, not by just the first field. Example. Many of the linked records are listed like XMANS, XMAND, MANGS, UMIMG, UMIMA I can’t remember all of these codes, but I know what I am searching for - so if I typed something like “Ear Mite” it would show me possible linked records to choose from, of which I would select UMIMG. Hopefully that makes sense - will try to attach an image. ... View more

Would be great if we could truncate the above or hide it - it takes up so much space in a view where I’d want my team / users to be navigating to views rather than making them. Thanks! ... View more

I’m currently maintaining dual contacts and calendar events, one set in Google, the other in Airtable. This isn’t ideal; if I make changes in the Google dataset I have to duplicate by hand in Airtable and vice versa. It would be far more useful, much less error prone to have Airtable sync with Google. Please, thank you. ... View more

Can we print/save as PDF charts in Blocks? ... View more

To keep this relatively simple, this suggestion boils down to one thing: enhancing view sections. While view sections are relatively new, they have already been incredibly useful for our team. They not only clean up our Views, but they help sort information into categories. However, I think View Sections may benefit from a couple of enhancements: Duplication would be incredibly nice. When you right click on a view, it has the option to rename, delete, and duplicate it. Why not add duplications to the sections as well? This would duplicate the section along with all of the views in the section. This could make doing views per collaborator much easier. The ability to nest sections could be handy too. We use our bases to organize trips. Ideally, we would have all trips in one base, and have views that filter applicants per trip. However, we have several collaborators per trip. Seemingly, it should be as simple as creating 1 view section per collaborator containing all of their trip views. However, we have several views that are useful for each trip. For instance, our trips table could have a gallery view, kanban view, and calendar view per trip. Thus, allowing for nested sections would be amazing. Changing the delete functionality would be great. In every other system that I have worked in, deleting a ‘folder’ deletes everything inside of it. Ideally, deleting a section would delete its views as well instead of moving them to the More section. This last suggestion, though small, may be better serviced by allowing batch changes to views through the use of check boxes. Like selecting multiple records, if you could select multiple views and either mass delete them or drag them all together to another folder, this could greatly increase productivity. ... View more