Field Manager
R
Rick DiChristofaro
I'd like to have the ability to use a custom field in multiple apps, or even potentially multiple solutions. I contacted support and they said that is under review on the internal roadmap, and I should maybe create a feature request to gauge interest.
Support said the current idea is to create predefined lists you can import as field templates. I like that idea. It would be great if the lists can be defined and accessible at the workspace level so they could potentially be used in any solution. Also, maybe have a settings option with a UI to see all predefined lists for each field.
Isaac Gutierrez
Merged in a post:
Master Field Types Manager
J
James Malin
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
Ara Bozadjian
We worked around this by creating a DATA Solution with multiple Tables for each 'Master List'. It actually gives you much more control and additional options.
Jon Darbyshire
Hello James Malin! I have a few more questions for you:
- How frequently do you anticipate needing to update the master list of field types?
- Are there specific field types or settings that are most critical to include in the master list?
- Would you need any specific permissions or access controls for managing the master list?
Vasken Bakalian
Rick DiChristofaro a predefined list of fields would be useful, vs the current auto-created 4 field types SS creates when creating a new app.
I've just requested a feature regarding this, you may check it here:
But your initial request sounds different. By a "Custom Field" Do you mean, a custom field type? or just a custom list of fields?
R
Rick DiChristofaro
Vasken Bakalian: Custom field is just a terminology choice. I can use use field. I just think custom field better describes the fact the field is created by a user and can have user entered data.
I think what you describe is best stated as an app template. I actually just searched that phrase in the feature requests and saw you posted that idea here https://smartsuite.canny.io/feature-requests/p/app-templates I like that idea.
It may make sense if SmartSuite had a template center. There a user could see solution templates, app templates, field templates, and doc templates (as another feature request suggested).
Vasken Bakalian
Rick DiChristofaro: Yup, the status is "Planned" now, so we will see the app templates soon.