Feature Requests

I would use the dollar sign "$" to show a rating of cost to the associated record.

Should be a simple request.... offer dollar sign as a choice ($). I would use it to show it the associated record is free or not

I have email templates where I'd like to be able to attach one or more documents. Would be nice if we could have granular merges of one or more attachments within an attachment field versus all of them. This way I could have a single attachment field for something like "Buyer Docs" Vs. Individual ones for "Buyer Rep," "Purchase Agreement," etc.

Hi SmartSuite team, I’d love a way to create a duplicate of an existing Formula or Lookup field as a “plain” field (Text or Number) that I can then safely use in subsequent formulas. The problem, Right now, when we try to build formulas on top of other formulas or lookups, we run into issues such as: Formula dependencies getting messy or unstable, Unexpected errors or recalculation problems when formulas reference other formulas, Difficulty chaining multiple calculation steps in a clean, reliable way For more complex setups (e.g. costing, pricing, production calculations), we often need a multi-step calculation where each step feeds into the next. Doing this with only formula-on-formula quickly becomes fragile. Proposed solution - Add an option on Formula and Lookup fields like: “Create static copy as…” – Text – Number – Currency (if applicable) This new field would: Store the resolved value of the original formula/lookup field, as a normal text/number field, Update automatically whenever the source value changes, Be treated by SmartSuite as a regular non-formula field, so it can be safely used in other formulas without circular reference problems or calculation errors Essentially, it’s a “materialized” version of the field we can chain off. Example use case We calculate a unit cost in a Formula field (involving lookups, conditionals, etc) We then want to: Apply tiered pricing, Add margins, Do rounding logic, Use it again in other apps via lookups If we could convert that formula result into a static Number field that stays in sync, we could build further formulas on it cleanly, without hitting the current limitations of formula-on-formula references.

Summary When adding a field while working inside a specific Tab → Section, the new field sometimes appears in a different tab/section. This breaks flow and forces users to hunt it down and move it. Proposed Solution Default the new field’s destination to the active Tab → Section. Show a small “Add to: [Tab] › [Section]” control with a dropdown to change the destination if needed. After creation, auto-scroll/flash to the new field for confirmation. Why it helps Matches user expectations (“add here means add here”) Reduces confusion and needless drag-and-drop Speeds up tab/section build-out Edge cases If no section is active, fall back to the last used section in the active tab (or the first section). If permissions prevent placement, default to the nearest allowed section and inform the user. Success indicators Less time spent finding new fields Fewer post-creation moves Higher satisfaction when building tabbed layouts

In a workflow where set fields need to be populated before pressing a button to trigger an automation, it would be great to be able to have the button "disabled" or greyed out" until those conditions are successfully met. This will prevent users from thinking they have successfully triggered the automation. It will also get rid of additional fields to act as confirmation (check box). Most importantly, it will alert the user that they are missing a critical step in the workflow.

There is a powerful feature called "log entries" that quickbase has for their notes field. Basically, there is a checkbox to turn on "log the edits on this field and show them in the field" It is a super userful way to capture ongoing updates in a simple text field. Within QuickBase there are options to: "Show the name and date on the same line as the entry" "Show the name and date on their own line" "Show new entries at the bottom of the field" "Show the time in addition to the date" "Show full names instead of user names" Here's a video explaining it: https://youtu.be/K1HszGGKfck?si=nK4X2FyzHZgP9B3m&t=167

I want to be able to specify the order a multi select appears. Currently I believe it orders them in first selected. User case - the multi select is used to define project stages for risks (design, build, use, maintenance, demo) - therefore I want the multi select to show the selected options in that order.

The [Current User] system variable should be accessible within the formula editor of the Button field. The variable would be resolved "just-in-time" when the button is clicked, avoiding the performance issues that might prevent its use in a standard, always-on Formula field. The Problem It is currently impossible to build a dynamic URL for a button that incorporates the details of the person clicking it. This prevents the creation of personalized, context-aware actions triggered by a button click, such as pre-filling a form with the current user's name or email. An attempt to build a dynamic URL like the one below fails because [Current User] is not recognized in the button's formula context: CONCAT(" https://form.smartsuite.com/xyz?Prefill_Requester= ", [Current User].Email) Proposed Solution & Implementation Enable the [Current User] object (and its properties like .Name and .Email) within the formula configuration of the Button field. Crucially, this would not require a constant, real-time recalculation of the field's value for every user viewing the record. Instead, the [Current User] variable would only be resolved at the moment the user actually clicks the button. This "just-in-time" calculation model avoids potential performance overhead while delivering the full dynamic functionality at the critical moment of user interaction. Business Impact This feature would unlock powerful, user-specific workflows directly from a button click, such as one-click approvals or task claiming. By making buttons context-aware, it would streamline processes, reduce manual entry, and significantly enhance the efficiency and automation capabilities of the SmartSuite platform.

We do a lot of inventory work. It would be helpful for our field techs to be able to use thier phones to capture serial numbers, mac addresses, potentially barcode using the camera on their phones. Currently typing in the field is working but very tome consuming and prone to error.