Feature Requests

We use the SmartDoc field to track actions in our sales process. It's a lot of work to manually add your name + current time every time you perform an action for a sales lead. A "signature" button to add a signature+timestamp would save a lot of work on a daily basis.

Ability to add record field values dynamically into the smartdoc. Similar to adding record field values into email automation.

Can you add an option to limit an attachment field to only contain one attachment? Let me breakdown problem to see if there is another solution: I am looking to have a specific attachment with a specific name, and multiple single attachments like a Letter of Proposal and then a Contract. Each one would have separate business logic around it. (Also in my case each document would need to connect to multiple different tables, like Deals, Companies, and Contacts. Currently managing this by creating a separate document table)

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.

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.

It would be helpful if the address field also retrieved the county for the address entered. We do a lot of work that is depenent on the county they are in.

Busy managers need to sign off many things every day. Would be great to be able to save a template of my own signature that I can just select by default instead of typing/drawin manually every time.

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

Add a YouTube link to the Social Network field. More companies and individuals now have their own YouTube channels.

It would be really nice if I can copy the item lists in a checklist field of an App and paste it in another checklist field of a different App. It would save a lot of my time in retyping everthing again.