Feature Requests

Would be cool to be able to set some permissions based on who is assigned to the particular record. This would allow everyone in a solution to still be able to access some information on the record while keeping some information private to only admins and the person assigned to that record. Case Study: We use formulas to determine the estimated budget for each task. Once an employee assigns themself to the task, another formula divides the budget by their individual pay per hour to give them an estimated amount of time on how long they have to complete the task. While we have most of these fields hidden from anyone who isn't management, we would like to also hide the "estimated time" field from anyone who is not assigned to that part of the task. That said, other aspects of the record should be viewed by other employees.

I would like the ability to create a rule that will only display a tab to my team and not all users. I don't see that option available when building my rules.

Many fields cannot be moved from the left side to the right side in the 70/30 layout. This really limits its use cases.

Inline edit just like on the dashboard widgets, but for in the record view for a linked record in table display

Apps with many sections & fields can require a significant amount of vertical scrolling to view an entire record. It would be nice to have the option to break sections & fields across horizontal tabs in record view. Important fields should remain visible at top of the record followed by tabs to group other fields.

Ability to sort linked records, in record view, so linked projects (records) will show in a-z or 1-9 order

I'm enjoying learning more about SmartSuite. It is a very versatile and powerful tool. One area that I think is underdeveloped is the Order and Order Line process. These are generic terms. A data model looks like this: Customer --< Order --< Order Line >-- Item. The "--<" means a one-to-many relationship. The ">--" means a many-to-one relationship. Order and Order Line are generic. Here are a handful of app relationships (or table relationships in data modeling terms): Vendor --< Purchase Order --< Purchase Order Line >-- Item Customer --< Sales Order --< Sales Order Line >-- Item Customer --< Invoice --< Invoice Line >-- Item Customer --< Return Order --< Return Order Line >-- Item Warehouse --< Transfer Order --< Transfer Order Line >-- Item My experience in SmartSuite (and maybe I'm doing this incorrectly) is: When creating a related line from the Order app detail screen, I'm taken to the Order Line detail screen. This is fine except I have to manually enter the related Order record as a link. It seems to me that SmartSuite should know that this Order Line needs to be linked to the Order from which I just came. I wasn't able to figure out how to have a lookup for the Title column. The best I could do was create a lookup for another column. I called that column SKU selector and the Title column as SKU, which automatically populates with the SKU selector. Too many steps. The SKU selector on the Order Line will set the SKU from the item. But I have to go half way down the Estimate Line layout to select it. It is more intuitive if it is the first field on the layout. The Price field is a lookup field; however, the price from the Item table doesn't come over when I link to an item in the SKU Selector field. On the Item app I have a Cost column and a Markup Percent column as a currency and percentage respectively. I have a Price column defined as a formula: [Cost] * [Markup Percent] + [Cost] to get the customer Price. But the result does not format as currency. I manually tried to force it by adding a "$" in front of the formula but then I lost the second decimal place if it was 0. I.e. $7.0 instead of $7.00 I hope this is not overwhelming. SmartSuite is really impressive! If you can crack this nut, then it would be a huge game changer for many service companies (think tree trimmers, gutter installers, HVAC, small appliance repair, electrical, pest control, etc.).

I think we miss an important feature to duplicate a record. This option will allow users to create a huge amount of records in a short period of time and then quickly update the necessary values which are different.

Action menu option to Remove Field from Display when inside a record

The ability to hide field or group of fields from record details based on a record condition. Example: If "Inspection" = No then do not display inspection fields. The condition could be set on a field by field basis but it would be even better if the condition could also be applied to a group/collection of fields. This would likely require the ability to assign fields to a group/category in field settings.