You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ddooley the "Save as..." vs the "Export to..." feature – should this only be supported in the "Save as..." feature?
I mention this because "Export to..." seems to be "owned" by the template repository. I'm not sure if it's something to force on every template if each implementation is meant to be different.
"Export to" involves conversion of a given schema to another, so will always involve a menu of specific target formats to map/convert fields to - each usually saved as tab separated data. That's why its different from "save as" which is not mapping fields, its just saving schema content with its own slot fields/names/structure.
Export to function currently often involves adding export.js script to fiddle with fields as they are transformed to target.
Indeed templates don't necessarily need an export option and in fact the "Export to" menu may list nothing if there is no export target predefined.
With issue #431 : rework the file saving to allow for multi-sheet Excel file saving.
The text was updated successfully, but these errors were encountered: