Feature Requests

The "Off/On" style of button works great, but "Off" and "On" isn't always relevant in terms of the use case. Being able to control what the "Off/On" states say in the button would be amazing. Examples might be: "Not Saved/Saved" "Not Sent/Sent" or even being able to have the "Off" state be blank, and the "On" state say something. 🙌 Does this affect operations? I suppose not, but would be a nice polished improvement to anyones setup.

The ability to create a Master List for field types would be amazing; My definition of this would be to be able to access saved or archived field types and their settings. In simple terms single select fields are rewritten a lot for clients and across aspects of applications Job Roles - CEO, CFO, CPO, COO - Instead of having to write this out in multiple solutions where relevant (its not a linked/lookup detail either), i would love to write it once, and save to a master sheet - allowing me to drop this information into other solutions, for multiple clients with a few clicks Main purpose for this would be to enable continous updates to master selections - if a new department is added, name is changed, this needs to be updated throughout the entire system - whereas if pulled from a master list - and the update occurs there, this happens across all aspects that are linked Overall this helps with the consistency of naming throughout an application and the continuity between applications the same. This in essence would allow for "default" appearances like status fields to be easily changed to naming conventions, colour schemes, again helping match colours and relevance for users when navigating the software and freeing up time for those finer touches

Hard to explain words but simple, when I'm in a record creation form and I have a record field I would like to not just unlink the record, but also have the option to delete it directly without opening the other table

For text and number fields, have the ability to require a specific number of characters. An example of this would be when we ask for an ID number that is 9 digits, we require them to input 9 digits to avoid typos.

It would be nice to have the ability to limit a user to select a certain number of items in multiple select field type.

I have created a solution to fill a process document. The following fields must be filled Part before Resin before and Part after Resin after Since there is a fixed relation between part and resin, I would like to connect the part with the resin for typing in. I have a single select field for the part and the same for the resin. I'd like to choose only the part, and get, either an auto-fill for the resin or a fltered list of resins. The idea is, to prevent choosing the wrong material for the parts. I tried to find something in the list below or a tutorial, but without success. Thanks, and kind regards,

I would like to have a dedicated view where I can see all the checklist items assigned to me. Currently, the system shows task assignments, but I need a way to track these checklist items separately as they are used as mini tasks in each project. This feature would help me manage my responsibilities more effectively without creating true tasks.

Currently we can set a default value for fields. But if I'm in a particular view, we sometimes need a different default field value (for that view). For example, if I have created a view of all tasks in the "office hour" category, I would want any new task created (while I am in that view) to default to the office hour category. And if I'm in another view (such as the "work hours" category), I would want any new task created to default to the work hours category. Right now, whatever the field default is will be applied no matter what view I am in. Notion is a good example of how this feature could work.

I need a way to restrict users from editing a field more than once per day. Ideally, once a field is filled out, it should no longer be editable until the next day. This would help in managing daily loan repayments without the risk of multiple edits.

If you want to make sure there aren't two entries with the same 'single select' selected, it would be great to have an option in the settings to "only select unused' selections so that when one selection was used, it will not show up as an option for subsequent records. Use Case: Interior Design. You have a single select filed with all the rooms you are designing but you don't want to accidentally have two entries for "dining room" by mistake. Any scenario where you want to make sure you only have one entry per single select option can use this setting. Thanks!