Use case or problem
At present when a new note is created by clicking the new button on the ‘bases’ table control area, the note is created with the properties that are selected for display in that view. In many, if not most cases, this is only a subset of the properties actually required for the note. It also does not allow for any pre-formatting of the markdown section of a note as would be achieved using a template.
Proposed solution
- When defining a new table view in the ‘bases’ component also allow a template file to be selected and associated with that view.
- When the New button in the ‘bases’ control area is clicked in order to create a new entry for that view it should also invoke the associated template when creating the file. If a template declaration is not present then revert to current behaviour.
Current workaround (optional)
Apply the required template to the note after it has been created. This requires an extra step and also re-ordering of the properties. It may also require some properties values to be added manually rather than being resolved by the template.
Related feature requests (optional)
Apply to all ‘bases’ views where a New button appears.